Dear all, I'm new here.
I'm trying to simplify a transition-crowded workflow of my company. I have a workflow with three teams that can pass issues to each other to allow each team to contribute to the solution. Every team have two statuses: "Waiting for that team" and "In progress on that team" (this because of specific SLAs).
When team A need to pass the issue to team B, the issue in progress on team A will be moved to waiting for the team B. Then, when the team B can take in charge the issue, they move the issue to in progress on team B, etc...
When a team find the solution, this team moves the issue in "Resolved". This can happen only if the issue is in progress on that team.
To simplify the worklow I would remove all the specific transitions from the various "In progress on a team" to "Resolved".
I seen in the documentation that each status, standard or custom, have a status category that can assume values like To do, In progress and Done.
I seen that in the workflow conditions on the transitions it is possibile to add a value field condition based on the field Status Category.
I tried various combinations as per the suggestions reported in this article https://community.atlassian.com/t5/Jira-questions/Value-Field-Condition-Current-Status-Status-Category/qaq-p/2229228 but I didn't get to the solution.
Now I'm wondering if there is a bug in Jira Cloud or if I'm making errors.
Any help is appreciated.
Hi @Davide Bortolotti (Jira Admin)
Welcome to the community.
Your interpretation is not correct.
A status has a defined status category, this can be To Do, In Progress or Done.
it is not that can be defined multiple categories.
So as an example in a workflow you have different statuses, some are in the category To Do (grey), some In Progress (blue and some Done (green)
Switching to a different status is possible on Status Category condition, this based on a Value condition, use the field status category and the option ID should be the value 1
To Do equals id 2
In Progress equals id 1
Done equals id 3
But way simpler is to use the previous status condition.
Dear @Marc - Devoteam
I think we're on the same page. I understood that each status is associated to a specific status category. My concern is to check the value of this status category in my workflow condition to enable a specific transition.
I tried to implement your suggestion to allow the transition from the "In progress on team A" status to the "Resolved" status:
But when I try to change the issue status, I cannot see the "Resolved" status in the drop down:
If I remove the condition on the status category, the "Resolved" status pops-up:
In my case using the previous status condition is not so simple because I have a large number of previous statuses and I want to create a scalable workflow avoiding to add to each transaction new statuses connected to new teams.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Davide Bortolotti (Jira Admin)
As i mentioned, the id for "Done" statuses (green) is 3, not 1.
So in your condition it should be equal to value 3
But as I mentioned, this is waiting for errors, it's better to use the condition:
previous status
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I tried even with the OptionID=3 but I'm experiencing the same behaviour like OptionID=1.
Is there any way to see somewhere the ID of the current status category related to the current status?
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Davide Bortolotti (Jira Admin)
It works on my end, but as I mentioned this way is not a sound way.
it's better to use the condition:
previous status
You can specify the exact status when using this condition, not a status category
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.