| Option | Description |
|---|
Least busy user (fewest unresolved issues assigned) | This is the default. The issue will be assigned to the user with the lowest number of assigned issues. If multiple users have the same number of issues assigned (e.g. none) the issue will be assigned to any of those users randomly. |
|
Least busy user (skip if current assignee is already a project role member) | The issue will be assigned to the user with the lowest number of assigned issues unless the current assignee already is a member of the specified project role. In that case the issue will not be re-assigned. |
Random user (skip if current assignee is already a project role member) | The issue will be randomly assigned to any member of the specified project role. |
Random user (other than current assignee) | The issue will be randomly assigned to any member of the specified project role unless the current assignee already is a member of the specified project role. In that case the issue will not be re-assigned. |
Previous assignee | The issue will be re-assigned to the member of the specified project role who has last been assigned the issue. If the issue has never been assigned to a role member, the issue will not be re-assigned. |
|
Previous assignee (or default user, if not present) | Variant where as a fallback the issue will be assigned to the default user. Default users can be specified using JWT project properties or JWT user properties. If the issue has never been assigned to a role member and no default role member has been specified the issue will not be re-assigned. |
|
| Previous assignee (skip if current assignee is already a project role member) | Variant where the issue will not be re-assigned if the current assignee already is a member of the specified project role. In that case the issue will not be re-assigned. |
Previous assignee (or default user, if not present / skip if current assignee is already a project role member)
| Variant with the default user fallback, unless the current assignee already is a member of the specified project role. In that case the issue will not be re-assigned. |
Next user (in selected group) using round-robin | The issue will be randomly assigned to any member of the specified group using the round-robin algorithm. What is a round-robin queue? The selected group in combination with the selected project role, define a round-robin queue. Each time the post function is executed in any workflow with the same configuration (i.e., same group and project role), the issue will be assigned to the next user in the round-robin queue.
The round-robin queue consists of all the users who are members of the selected group and project role at the same time. |
|
Next user( in selected group) using round-robin (skip if current assignee is already a project role member) | The issue will be randomly assigned to any member of the specified group using the round-robin algorithm unless the current assignee already is a member of the specified project role. In that case the issue will not be re-assigned.. |
Default user | The issue will be assigned to the default user.
The user must be added to the project role in the Users and roles settings in the project configuration if you use any of these tools. In addition, if you use both of them, the default users set with JWT project properties will take preference over those set with JWT user properties. |
|
Default user (skip if current assignee is already a project role member) | Variant where the issue will not be re-assigned if the current assignee already is a member of the specified project role. In that case the issue will not be re-assigned. |
Configuration
Use cases and examples