Our new Appfire Documentation Space is now live!

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

Set issue security level based on user's project role

Owned by Radhika Vijji. (Unlicensed)
Last updated: Aug 07, 2018

A workflow post-function that sets the Security Level of the current issue based on the project role to which the current user belongs.

To add the 'Set issue security level based on user's project role' post-function to a transition :

  1. Click Edit for the workflow that has the transition you wish to configure 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 Set issue security level based on user's project role 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 issue security level from the Issue Security Level drop-down.
  9. Click on Add to add the post-function to the transition.

Related links :

For information on where the post-function needs to be placed on a transition, see Placing post-functions on a transition.

Refer to the Use cases for post-functions page for use cases for this post-function.

When you add this post-function to a transition and trigger the transition, the add-on sets the selected issue security level on the current issue, if and only if the current user belongs to the selected project role.

This function can be used on the Create transition to set a different issue security level depending on whether the issue is being created by an internal user or by an external user (e.g. a customer).

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, 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.