Problem
When using the Atlassian MCP server to transition Jira issues via transitionJiraIssue, the API returns a permission error if the project's transition screens include the Sprint field (customfield_10020):
"customfield_10020": "We couldn't make that happen because you don't have Schedule Issues permission."
This happens even though the authenticated user does have "Schedule Issues" permission in their Jira project. The same user can successfully perform the transition via the Jira web UI (browser session auth).
Root Cause
The MCP server's OAuth configuration currently requests these scopes:
read:jira-work
write:jira-work
It does not request write:sprint:jira-software, which is required for the API to interact with the Sprint field during transitions. When Jira validates the transition, it checks the OAuth token's scopes against all screen fields -- including Sprint -- and rejects the request because the token lacks the sprint scope.
Impact
Any Jira project that has Sprint on its workflow transition screens (which is common in Scrum-based projects) cannot use transitionJiraIssue via MCP. This blocks automation of the full issue lifecycle (e.g., Opened → Assessed → Analyzed → Implemented → Closed).
Affected tool: transitionJiraIssue
Proposed Fix
Add write:sprint:jira-software to the OAuth scope configuration so the MCP token can pass Sprint field validation during transitions. This doesn't mean the MCP needs to actively manage sprints -- it just needs the scope so Jira doesn't reject transitions that have Sprint on the screen.
Environment
MCP Server: https://mcp.atlassian.com/v1/mcp
Client: Cursor IDE (plugin-atlassian-atlassian)
Jira: Cloud (company-managed project, Scrum workflow)
Reproduction
Set up a Jira Cloud project with a Scrum workflow where transition screens include the Sprint field
Authenticate via MCP (mcp_auth)
Call transitionJiraIssue on any issue
Observe: "customfield_10020": "We couldn't make that happen because you don't have Schedule Issues permission."
Perform the same transition via Jira web UI -- succeeds
Workaround
Currently users must transition issues manually via the Jira web UI. Project admins can also remove the Sprint field from transition screens as a workaround, but this changes the workflow for all users.
Problem
When using the Atlassian MCP server to transition Jira issues via transitionJiraIssue, the API returns a permission error if the project's transition screens include the Sprint field (customfield_10020):
"customfield_10020": "We couldn't make that happen because you don't have Schedule Issues permission."
This happens even though the authenticated user does have "Schedule Issues" permission in their Jira project. The same user can successfully perform the transition via the Jira web UI (browser session auth).
Root Cause
The MCP server's OAuth configuration currently requests these scopes:
read:jira-work
write:jira-work
It does not request write:sprint:jira-software, which is required for the API to interact with the Sprint field during transitions. When Jira validates the transition, it checks the OAuth token's scopes against all screen fields -- including Sprint -- and rejects the request because the token lacks the sprint scope.
Impact
Any Jira project that has Sprint on its workflow transition screens (which is common in Scrum-based projects) cannot use transitionJiraIssue via MCP. This blocks automation of the full issue lifecycle (e.g., Opened → Assessed → Analyzed → Implemented → Closed).
Affected tool: transitionJiraIssue
Proposed Fix
Add write:sprint:jira-software to the OAuth scope configuration so the MCP token can pass Sprint field validation during transitions. This doesn't mean the MCP needs to actively manage sprints -- it just needs the scope so Jira doesn't reject transitions that have Sprint on the screen.
Environment
MCP Server: https://mcp.atlassian.com/v1/mcp
Client: Cursor IDE (plugin-atlassian-atlassian)
Jira: Cloud (company-managed project, Scrum workflow)
Reproduction
Set up a Jira Cloud project with a Scrum workflow where transition screens include the Sprint field
Authenticate via MCP (mcp_auth)
Call transitionJiraIssue on any issue
Observe: "customfield_10020": "We couldn't make that happen because you don't have Schedule Issues permission."
Perform the same transition via Jira web UI -- succeeds
Workaround
Currently users must transition issues manually via the Jira web UI. Project admins can also remove the Sprint field from transition screens as a workaround, but this changes the workflow for all users.