Skip to content

feat(skills): add manage-jira-releases skill#176

Open
shubh1112 wants to merge 1 commit into
atlassian:mainfrom
shubh1112:feat/manage-jira-releases
Open

feat(skills): add manage-jira-releases skill#176
shubh1112 wants to merge 1 commit into
atlassian:mainfrom
shubh1112:feat/manage-jira-releases

Conversation

@shubh1112

Copy link
Copy Markdown

Summary

  • Adds a new manage-jira-releases skill that enables creating, updating, listing, and releasing Jira project versions directly from MCP-connected clients
  • Addresses the gap where users can set fix versions on issues but cannot create the versions themselves without switching to the Jira UI
  • Follows existing skill patterns: YAML frontmatter, human-in-loop confirmation, structured workflow steps, edge case handling, and cross-skill integration guidance

Closes #66

Details

The skill supports:

  • Create version — with name, description, start date, and release date
  • List versions — view all versions in a project with their status
  • Update version — modify description, dates, or name
  • Release version — mark a version as released with appropriate date

References the following MCP tools:

  • createJiraVersion
  • getJiraProjectVersions
  • updateJiraVersion
  • getVisibleJiraProjects
  • getAccessibleAtlassianResources

Test plan

  • node scripts/validate-template.mjs passes with no errors
  • Verify skill is discoverable via Claude Code / Cursor plugin
  • Test createJiraVersion flow against a live Atlassian Cloud site
  • Confirm human-in-loop prompts appear before any mutating action

@atlassian-cla-bot

Copy link
Copy Markdown

Thank you for your submission! Like many open source projects, we ask that you sign our CLA (Contributor License Agreement) before we can accept your contribution.
If your email is listed below, please ensure that you sign the CLA with the same email address.

The following users still need to sign our CLA:
❌shubh1112

Already signed the CLA? To re-check, try refreshing the page.

@shubh1112 shubh1112 requested a review from dmiller113 as a code owner June 15, 2026 16:11

@jatinkrmalik jatinkrmalik left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your submission! Like many open source projects, we ask that you sign our CLA (Contributor License Agreement) before we can accept your contribution. If your email is listed below, please ensure that you sign the CLA with the same email address. **The following users still need to sign our CLA:**❌shubh1112

Already signed the CLA? To re-check, try refreshing the page.

@shubh1112 Before we can review the pull request, you will need to sign the CLA here. 👆

@decompil3d

Copy link
Copy Markdown

@atlassian-cla-bot check

@decompil3d

Copy link
Copy Markdown

CLA signed. @jatinkrmalik you are good to proceed with review.

@shubh1112 shubh1112 requested a review from jatinkrmalik June 16, 2026 06:07

@shubh1112 shubh1112 left a comment

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could any of CODEOWNERS review this, please?

@zayd-gener8

Copy link
Copy Markdown

@jatinkrmalik can you or someone please review this as its super useful! Thank you!

@zayd-gener8

Copy link
Copy Markdown

@jatinkrmalik

Copy link
Copy Markdown
Collaborator

Looking into it today.

@zayd-gener8

Copy link
Copy Markdown

@jatinkrmalik Any news?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add tool to create Jira project versions/releases

4 participants