When you add this post-function to a transition and trigger the transition, the add-on looks for the last assignee (excluding the current user) of the issue who belongs to the selected Project Role
. If such member is found, it assigns the issue to that user. If not, the Assignee field is not modified. By default, while searching for the last assignee belonging to the selected Project Role
, the current assignee and the reporter are not considered.
Options
- Include Reporter
If no previous assignee belonging to the selected Project Role
was found, and the reporter belongs to the selected Project Role,
then the issue is assigned to the reporter.
- Include Current Assignee
If the current assignee belongs to the selected Project Role,
then the issue stays with the current assignee.
- Skip Inactive Users
The inactive users are skipped while searching for the last user of the selected Project Role
.
Action
Customize the assignment using the below actions:
- Force assignment (default) - Forcibly assigns the issue to the last role member of the selected
Project Role
. In this case, any user selected in theAssignee
field on the Transition screen (if any) is ignored. - Only if "Automatic" - Assigns the issue to the last role member of the selected
Project Role
only if the user selectsAutomatic
in theAssignee
field on the Transition screen. - Use selected assignee if changed on the transition screen - Assigns the issue to the last role member of the selected Project Role only if the assignee is not changed (or set to
Automatic
) on the Transition screen.
Conditional execution
To execute this post-function based on the result of a groovy expression see Conditional execution/validation using a Groovy expression.
Error Handling
By default, all errors (Java Exceptions) raised by this post-function, including those raised by custom Groovy scripts, will be logged in the JIRA log file but will not be reported to the user and will not prevent the transition from completing. However, when designing new workflows or troubleshooting them, it is more convenient to be notified immediately of any such error during the execution of the transition. On development and staging Jira instances, you can activate error reporting for all JMWE post-functions on the JMWE configuration page, and it is recommended to do so. But on production Jira instances, For example on the production Jira instances you might want to show errors only for only for the post-function(s) being worked on, in order to avoid disrupting other workflows. To make errors errors raised by the the current post-function prevent the transition from completing and show the error in the browser, select Make transition fail when an error occurs in this post-function
.
If you want to show all the errors, either only to the admins or to all users, configure the option globally on the JMWE configuration page. For example, on development and staging Jira instances, you can activate error reporting for all JMWE post-functions, to display all the errors and it is recommended to do so, and on production Jira instances you might want to activate error reporting only to administrators so that they can be made aware of configuration errors.
Note |
---|
When the option is selected on a post-function, it overrides the configuration on the JMWE configuration page. |