You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi everyone. I have a Jira Project with a very complex workflow with more than 70 transitions altogether. I have 26 statuses, 50 transitions on the normal workflow, and I also have all-to-all transitions for each of the 26 statuses (only admins are allowed to perform this transitions). So, normal users doesn't have any issues as they can see up to 5 transitions from the normal workflow (for example from Backlog to Analysis, Development, Cancelled etc). We have 2 transition buttons and the rest nest inside the workflow button. Everything's fine. But the admins are allowed to perform all all-to-all transitions (which is 26 tranisitons) + the normal transitions from the specific status that the given issue is in. So, for a given issue, an admin can perform up to 32 transitions, and the workflow button can only nest up to 25 transitions, it seems. The remaining 7 transitions are lost. How can I fix this?
I know it's not a good practice to have 70+ transitions in one workflow, but that's what the team wants and I have to find a solution to this. I advised them that they can change perform the transitions through bulk change if they need to perform one of the lost transitions, but interestingly these transitions were not an option in the Bulk Change's transition issues option either.
What can I do to make all possible transitions visible inside the workflow button?
For this specific case I think taking 4-5 transitions out of the Workflow button could help, I mean they can be on the issue page before the workflow button, and the rest can fit inside the button. But that would require shutting down the instance and would cause some problems. So, please help me finding another solution.
I think the optimal solution to this specific case would be limiting the number of all-to-all transitions and only keeping the necessary ones. For example keeping all-to-all transitions only to to do type statuses, so, if an issue is accidentally transitioned to another status the admin can fix this mistake by returning the issue to the nearest to do status and the actual assignee can transition it to an in progress type status when he or she actually starts to work on it. This way admins would still have the flexibility they need, and no transitions would be lost. If there won't be any better ideas to address this issue, I think this could be a viable options for those who face the same issue in the future.
Hi @Tarlan Mustafayev , in your complex Jira project with over 70 transitions, where admins are facing issues accessing all possible transitions due to a limitation in the workflow button's capacity, consider reorganizing the transitions to address the problem without shutting down the instance. As you suggested, moving a subset of transitions outside the workflow button could be a viable option. Since this may pose challenges without shutting down the instance, explore alternative solutions such as creating a custom solution using Jira apps or scripts that allow dynamic visibility of transitions based on user roles or conditions. Additionally, check if any Jira plugins or updates provide enhanced functionality for handling extensive workflows. Engage with the Jira community or support for insights and consider implementing best practices for optimizing workflow efficiency while accommodating your team's preferences.
Hi Kaljan, thank you for your prompt response. I've looked up for some easy plugins for like an alternative workflow button with a scrollbar for example, but couldn't find anything yet. I think having 70+ transitions is a unique challenge of which solution is not commercially viable. On second thought I think limiting the number of all-to-all transitions for only to-do type statuses would solve the problem in the easiest way and I decided to write this as a comment if someone else would need it in the future too. Thank you again, for your answer