In Jira project dashboard duplicate statuses appearing in the status dropdown (e.g., Transition to >

[Lavanya Elango-C]

In Jira project dashboard duplicate statuses appearing in the status dropdown (e.g., Transition to > Ready for QA, and also Dev In Progress → Ready for QA, etc.)

[Lavanya Elango-C]

Yes, I do have Site Admin access, and I’m the one who made the update to the workflow.

The reason for adding the "All " global transition was due to a user request. They needed the ability to revert issues to a previous status in their Jira project. To support that flexibility across various scenarios, I added the global transition so users could move back to that status from any other status.

If there’s a better way to manage this, please let me know. 

[Trudy Claspill]

Hello @Lavanya Elango-C 

Welcome to the Atlassian community.

That indicates that there are two transitions available to change the issue from the current status to the Requirement Review With App... status.

Can you share an image of the  Workflow Diagram with us for the workflow that applies to the issue type you are viewing? We can then point out the two transitions.

[Lavanya Elango-C]

[Trudy Claspill]

Thank you for that image. That is helpful.

As I suspected you have two transitions to the destination status.  Wherever you see an arrow between two statuses, that is an explicit transition between those two statuses. That is #1. Where you see "ALL --->" pointing to a status is a Global Transition. That indicates you can transition from ANY status to the one indicated by the arrow. That is #2.

By default when workflows are created, they use just Global Transitions. An administrator can change the workflow to add specific transitions to enforce a specific flow of an issue from one status to another.

Conditions can be added to transitions also to limit who sees which transitions. For instance, the Global Transitions could have a Condition that makes them visible only to Project Administrators, while the specific transitions are visible to all users. In that case a Project admin would see both the specific transition and the Global transition, as you showed in your original image.

Are you responsible for the addition of the specific transitions in this workflow?

I would ask the admin who made the change what they intended/expected to happen by making the change. By understanding the intention we can then ask additional questions and provide suggestions for changes, if that is needed to achieve the intention.

[Lavanya Elango-C]

Yes, I do have Site Admin access, and I’m the one who made the update to the workflow.

The reason for adding the "All " global transition was due to a user request. They needed the ability to revert issues to a previous status in their Jira project. To support that flexibility across various scenarios, I added the global transition so users could move back to that status from any other status.

If there’s a better way to manage this, please let me know. 

[Trudy Claspill]

Hello @Lavanya Elango-C 

You have to decide what transition paths you want to allow, and who should be allowed to execute them.

If all users (who can transition issues in this project) need to be able to revert issues, what is the purpose of having a specific transition flow with individual transitions from one status to another?

If there are no Conditions applied to the transitions the users will see multiple transition options for each destination Status that has more than one transition arrow point to it.

Global transitions have not "forward" or "revert" direction inherent in them. They can be used to skip over statuses moving "forward" and "reverting". There will be enforced flow through the statuses when all statuses have an incoming Global Transition.

If there are prescribed paths to move "forward" and "revert" between statuses, enforcing those paths requires individual transitions between the statuses. If the ability to ignore the prescribed path should be permitted for only a subset of users, then Conditions need to be added to the Global transitions.