-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
3
-
Severity 3 - Minor
-
1
-
Issue Summary
While sending a GET request to the Get all status categories API endpoint, you can check the id's and names of the respective status categories in your instance. Using that information, you should be able to set a workflow (Value field) condition in order to restrict issues in a specific status category from being able to use the given transition.
Steps to Reproduce
- Check the id's/names using the above API endpoint
- Navigate to Project settings -> Workflows and edit the workflow for the given issue type(s).
- Add a 'Value field' condition on the transition in question, for instance, 'Status Category' = 'To Do' as a 'String' OR 'Status Category' = '2' as an 'Option ID'. Keep in mind those are only examples, the id might differ in your instance and you may try to use a different condition (like '!=') instead.
Expected Results
The given transition isn't visible if the above condition isn't met.
Actual Results
The given transition is visible in case you used the '!=' condition, and not visible if '=' was used, despite matching id/name of the status category.
Workaround
- The only (close) workaround is to use the 'Previous Status Condition' condition, although it might come with additional administrative effort depending on the number of statuses in the given status category.
Community discussion: https://community.atlassian.com/t5/Jira-questions/Value-Field-Condition-Current-Status-Status-Category/qaq-p/2229228
- is related to
-
JRACLOUD-74787 Allow StatusCategory to be used instead of specific Status values in workflow configurations
- Gathering Interest