User is unable to change Story to or from Accepted state in Jira Align
Platform Notice: Cloud and Data Center - This article applies equally to both cloud and data center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
User is unable to change a story to “Accepted” state as this option is grayed out.
For a story already in the “Accepted” state, user is unable to change the state back to a previous state as those options are grayed out.
User appears to have the correct role and system permissions.
Environment
Jira Align
Cause
There are other conditions that need to be met apart from system permissions.
Solution
To be able to accept stories in Jira Align:
The user must be a member of the Agile team that is assigned to the Story (so they are present on the members tab of the Team profile)
The Story must be assigned to a Sprint
The user must possess either “Product Owner” or “Analyst” roles in the given sprint (so they are present on the members tab of the Sprint)
For items synced with Jira, if the Accepted Date has been set (in addition to the Accepted State) as shown in the below image then the user will have to change the 'Done' State in Jira, which after a sync operation will unlock the state field in Jira Align.
Related Content
You can see more details on Agile team roles on the link 10X-Assign-Team-Roles
Was this helpful?