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

[shubh1112]

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

Preview endpoint caveat

The Jira project version tools this skill relies on (createJiraVersion, getJiraProjectVersions, updateJiraVersion) are currently available only on the Rovo MCP v2 preview endpoint (https://mcp.atlassian.com/v1/mcp/preview), not the default endpoints (https://mcp.atlassian.com/v1/mcp/authv2 / /v1/mcp). See #66 for the maintainer note on preview availability.

To keep clients on the default endpoint from attempting unavailable tool calls, the skill is explicitly documented as preview-only. Changes made:

• Prominent preview-only notice at the top of SKILL.md, listing the preview endpoint URL
• A Prerequisites section with a compatibility check — verify the version tools are present before any call, with a ready-to-use message pointing users to the preview endpoint if they are not
• Added step 0 (Check Compatibility) to the Core Workflow sequence
• A troubleshooting entry for the wrong-endpoint case
• A Quick Reference reminder that the tools are preview-only

.mcp.json and the README are intentionally left on the default endpoint so repo-wide defaults are unchanged; the preview caveat can be dropped once these tools graduate to the default endpoint.

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

[atlassian-cla-bot]

Hooray! All contributors have signed the CLA.

[jatinkrmalik]

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]

@atlassian-cla-bot check

[decompil3d]

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

[shubh1112]

Could any of CODEOWNERS review this, please?

[zayd-gener8]

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

[zayd-gener8]

Can someone review please? @shubh1112 @iosamaatlassian @SreeNerella @dvenkatesh07 @blakewang-atlassian @jvarghese2 @ekahinga @mustaphaturhan @jatinkrmalik

[jatinkrmalik]

Looking into it today.

[zayd-gener8]

@jatinkrmalik Any news?

[KSHITIZ6341]

One endpoint compatibility issue before merge.

[KSHITIZ6341]

I think this needs to be resolved before merge because this skill documents createJiraVersion, getJiraProjectVersions, and updateJiraVersion as normal callable tools, but the linked issue now says project-release tools are only available on the preview endpoint.

The repo's default manifests and README still point users at https://mcp.atlassian.com/v1/mcp/authv2 / /v1/mcp. If the skill ships before those tools are available on the default endpoint, clients following it will attempt tool calls that are not present.

Suggested direction:
Either hold the skill until the version tools are on the default endpoint, or make the skill explicitly preview-only and document the required endpoint/compatibility check before any workflow uses these tools.

Reference: #66 (comment)

[shubh1112]

Good catch — confirmed. Per the maintainer note on #66, the version tools are currently preview-only (Rovo MCP v2), and the repo defaults point at the production endpoint.

I have taken the preview-only path in 38b9887: the skill now carries a prominent notice, a Prerequisites compatibility check (verify the tools are present before any call, with a clear message pointing users to https://mcp.atlassian.com/v1/mcp/preview if they are not), a troubleshooting entry, and a Quick Reference reminder. Clients on the default endpoint will no longer attempt unavailable tool calls. Left .mcp.json/README on the default endpoint intentionally so repo-wide defaults are unchanged; the preview caveat can be dropped once these tools graduate to the default endpoint.

[KSHITIZ6341]

Thanks — the preview-only notice addresses my original endpoint concern.

One compatibility issue remains: according to the current preview documentation, Jira project-version capabilities are discovery operations invoked through discover and execute; they are not exposed directly in tools/list. The documented mutation operation is manageJiraProjectVersion, rather than createJiraVersion or updateJiraVersion.

As written, a correctly configured preview client may fail the compatibility check and be treated as connected to the wrong endpoint. The examples would also attempt undocumented direct calls.

Could you update the skill to:

1. Check for discover and execute.
2. Discover getVisibleJiraProjects, getJiraProjectVersions, and manageJiraProjectVersion.
3. Invoke them through execute using their discovered schemas.

Reference: https://developer.atlassian.com/cloud/rovo-mcp/preview/tools/