Our new Appfire Documentation Space is now live!

Take a look here! If you have any questions please email support@appfire.com

Assign to last role member

Owned by Radhika Vijji. (Unlicensed)
Last updated: Nov 11, 2021 by Sireesha Dugginapeddi [Appfire] (Inactive) (Deactivated)
3 min read

Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here.

A workflow post-function that assigns the current issue to the last assignee who belongs to a selected project role.

To add the 'Assign to last role member' post function to a transition: 

  1. Click Edit for the workflow that has the transition you wish to add the post-function on.

  2. In the Workflow Designer, select the transition.

  3. Click on Post Functions in the properties panel.

  4. Click on Add post function.

  5. Select Assign to last role member from the list of post-functions.

  6. Click on Add to add the post-function on the transition.

  7. Select the project role from the Project Role drop-down.

  8. Select the options provided to add the required parameters.

  9. Click on Add to add the post-function to the transition.

Note you need to publish the workflow

Related links :

 

 

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 a 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 the Assignee 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 selects Automatic in the Assignee 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. For example, on the production Jira instances, you might want to show errors only for the post-function(s) being worked on, in order to avoid disrupting other workflows. To make errors raised by 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.