Introduction
This post function allows you update a user field (assignee by default, but it can be any user picker field). Users can be selected from group or roles (multiple selection is allowed). There are several user selection strategies available.
This powerful post function can be used in following scenarios (e.g.):
- Automatic issues assignment to service desk operators (randomly)
- Workload optimization
- Round Robin issues assignment
- Assign an issue to most experienced user
| Element summary | |
|---|---|
| Status | CURRENT |
| Version compatibility | 6.0.1 - Latest |
| Supported | Yes |
| Introduced in version | 1.0.0 |
Post function parameters
Post function takes following parameters:
- Field to be updated (a field to assign user) - field to be updated in this post function. It's Assignee by default, but you can update any user field in your issue.
- Check assignable permission - prevents from assigning issue to user who doesn't have assignable permission. If unchecked every user can be assigned.
- Group/Role selector (assign someone) - groups or roles to select users to be selected. You can choose one or more elements.
- Assign strategy - method of user selection
- Assign randomly - select random user from groups or roles selected above.
- Assign alphabetically - select user in alphabetical order (by username). JIRA remember last selected user (for each project and group/role separately). It implements Round-Robin (or carousel) alghoritm. If last user is reached, selection starts from beginning.
- Assign to user who is in highest number of issues - selects user who is (in selected field) in highest number of issues returned by JQL Search.
- Assign to user who is in lowest number of issues - selects user who is (in selected field) in lowest number of issues (or no issues) returned by JQL Search.
- Assign to user from first JQL issue returned - first applicable user will be used.
- Assign randomly - select random user from groups or roles selected above.
- Assign only when empty - runs only if given field is not empty
- Issue relation and JQL - optional - see below.
- Exclude users from assigning - allows you to exclude some users (e.g. exclude reporter from candidates to assignee)
Working with related issues Related issues can be selected by using two inputs: Issue Relation - where you can choose a relation with the current (transitioned) issue; JQL - you can put your JQL text to filter some issues from the results. If you leave the JQL Field empty, all issues in a given relation are taken into account. In the example above you wanted to execute a workflow function on subtasks of the current issue and take additionally only the ones with the "Sub-task" and priority="High" type. In the JQL field you can put some text tags to be replaced with actual values of the current (transitioned) issue: $$CURRENT_DATETIME$$ $$ASSIGNEE$$ $$CURRENT_STATUS_CATEGORY$$ The JQL field has a built-in validation feature. If your query is incorrect, you will see a red sign next to the JQL field and an error description as shown below:
Tags
Tag Description The current date and time. $$CURRENT_USER$$ The name (login) of the current user. $$ISSUEKEY$$ The key of the current issue. $$ISSUEID$$ ID of the current issue. $$REPORTER$$ The current issue reporter's name. The current issue assignee's name $$PROJECTKEY$$ The project key. $$CURRENT_STATUS$$ The current issue status. $$ISSUETYPE$$ The issue type. $$CREATED_DATE$$ The date when the issue was created. A status category of the current issue (To Do, In Progress or Done). $$TRANSITION_NAME$$ The name of an actual transition (doesn't work in Conditions) $$TRANSITION_ID$$ ID of an actual transition (doesn't work in Conditions). $$TRANSITION_COMMENT$$ The content of a transition comment (doesn't work in Conditions). 
Example of usage
