User in Field(s) Condition
The User in Field(s) Condition controls if a user can transition an issue based on whether or not they are added in any specified field. If the fields contains users, the condition checks if the current user is selected. If the fields contains groups, the condition checks if the current user is within any of those selected groups.
The following fields are supported:
- Custom fields - user picker, multi-user picker, group picker, multi-group picker.
- System fields - reporter, assignee, watcher, request participants.
There are two ways to use this condition, depending on if you choose to invert the condition or not:
- (Normal) The transition is allowed if the current user is listed in at least one of the specified fields.
- (Inverted) The transition is allowed if the current user is not listed any of the specified fields.
For example:
- I have a Hiring Manager custom field on my recruitment project. I want to ensure only the hiring manager can transition the recruitment ticket to Offer Accepted.
I have a Team Members multi-user picker field auto-populated with a list of all the users in the reporter's team. I want to restrict these users from transitioning the issue to Escalated.
You can add this condition to any transition except the Create transition.
Select the User in Field(s) Condition [ScriptRunner] condition.
For details on how to navigate to ScriptRunner workflow functions, see Navigating to Workflow Functions.
Enter a description of the condition in Note.
Enter one or more User Field(s). Only users added in any of these fields are able to transition the issue. If inverted, users added in the specified fields will not be able to transition the issue.
Make sure your selected fields are on the screen for the project(s) your condition applies. This condition function will check field values even if they are not on the screen.
- Optionally, select to Invert Condition.
Click Update.