...
For information on where the post-function needs to be placed on a transition, see Placing post-functions on a transition.
When you set add this post-function on to a transition and trigger the transition on an issue, the add-on checks for the default member of the selected Project Role
. If such user member is found, it assigns the issue to the fetched user. If not, the issue is assigned to a random member of the selected Project Role
. If there are multiple default members, a random member is picked and the issue is assigned to the picked user.
...
If you want a specific user to be picked, you must either use the User Property trick (explained below) or use a more specific Role (one that contains only a single user).
Since JIRA does not support the notion of a default member for project roles, the Assign to role member function identifies the default member of a project role by going through all the members of the project role looking for a User Property with the following two characteristics:
- Property key: defaultAssignee
- Property value: contains a comma-separated list of entries in the form ProjectKey -> *RoleName. *For example:
TST -> Developers, JMWE -> Testers |
For backward compatibility, the following two forms are also supported:
- Property Key: {ProjectName}x{RoleName} (for example: CoolProjectxQAMembers)
- Property value: "default" (without the quotes)
Or: (since 1.5.3)
- Property Key: defaultAssignee{n} (where n is a number from 1 up, for example: defaultAssignee1)
- Property value: {ProjectName}x{RoleName} (for example: CoolProjectxQAMembers)
Customize this post-function using the additional options provided as a part of the post-function. The options are:
...