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
I would like to restrict a group or user from performing a particular transition in a workflow.
If my workflow has 'To do' 'In progress" and 'In review' statuses, The user or group can perform transition from 'To do' to 'In progress' but not from 'In progress' to 'In review'.
Please share your suggestions.
The solution is:
Or alternative solution, you can use also project role:
you can only allow users or groups to perform a transition. Restrictions aren't possible. This meens if just some of your users should only be allowed to execute certain transitions these need to have a "User in Group" of "User in Projectrole" etc. condition. For details, check the documentation:
As others have already answered, this is not possible off-the-shelf. You must use a third-party app to create a negative condition that prevents a specific user group from transitioning.
In addition to the suggestions from @Rezgar Cadro _Totem Dev_, I will add Jira Miscellaneous Workflow Extensions (JMWE) to the list of options. I believe it is slightly less expensive than some of the others. In JMWE, you can create a User Condition that uses a custom expression to create a negative restriction:
The completed condition looks like this:
And here's a Scribe I created with step-by-step screenshots.
To answer the question less directly, I would avoid this pattern. In my experience, it can be more problematic (less maintainable, harder to troubleshoot) than explicitly allowing users, groups, and project roles.
So, if you have the flexibility, I would design a permission scheme based on groups or project roles that explicitly allow the transition rather than disallow it. This would be easier to maintain, and you can stick with Jira's native conditions.
A common difficulty with the negative pattern is that you can have users assigned to multiple groups. So, for example, suppose we implement a condition that prevents "User Group B" from completing a transition. If a user is assigned to both User Group A and User Group B, they will be prohibited from the transition even though their membership in User Group A would otherwise allow it.
But of course, I have no context about your use case, so I don't know if this problem is relevant to you. ;-)
While you can't do that with built-in workflow conditions, here are a few options:
You can Edit the Workflow and add a Rule to do this as mentioned here - https://support.atlassian.com/jira-software-cloud/docs/add-or-remove-workflow-rules-in-team-managed-projects/
Specifically, you'll be looking for this type of rule - "Restrict who can move an issue"
Hi, you can add conditions on a transition to control whether it can be executed by a user or groups. Have a look here: https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/
You've got some good answers here. Only thing I would add is to make sure you are not using Simplified Workflow and are instead using Jira/Customized Workflow?
If you are using customized workflow, you can add a condition to every transition that you want to restrict. For example, using the "User is in project role" condition: