Cloud Migration Resources
Planning a Jira Cloud migration? These resources can help you get started:
→ JMWE Cloud features – Review Cloud features and understand key differences between DC and Cloud.
→ Migration support from Appfire – Learn how we can help you migrate smoothly.
Set Issue Security Level
A workflow post-function that sets the Security Level of the current issue based on the project role to which the current user belongs.
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).
Warning: JMWE cannot take any actions or make any changes to an issue that has a Security Level to which the JMWE Addon user does not have permissions. This includes, but is not limited to, setting the Security Level of an issue. Additionally, if the Set Issue Security Level post function is used to change an issue’s Security Level to a level at which JMWE does not have permissions, it creates a scenario where JMWE cannot make any changes.
To add the 'Set Issue Security Level' post function to a transition:
Click Edit for the workflow that has the transition you wish to add the post function to.
Select the transition in the Workflow Designer.
Click Post Functions in the properties panel (or select the Post Functions tab).
Click Add post function.
Select Set Issue Security Level from the list of post functions.
Click Add. The Set Issue Security Level post function screen will open, where you can configure the post function as needed. See below for more information.
Click Add to complete the configuration and add the post function to the transition.
After adding, move the post function to the appropriate position according to Placing post functions in a transition.
Configuration options
Project Role - Select the Project Role to which the user who triggers the transition must belong; if the user belongs to that Project Role, the issue will be set to the selected security level.
Issue Security Level - Select the security level for the issue.
Advanced options
Expand this section to see advanced configurations including which user will run the post function, conditional execution, and delayed execution.
Conditional execution
Check Run this post-function only if a condition is verified to execute this post function based on the result of a Nunjucks template; see Conditional execution.
Delayed execution
Post functions are provided with an option to delay execution for a set number of seconds using the Delayed execution option (Figure 1, right). To delay execution, select the number of seconds to wait until the post-function is run; any value between 1 second (the default) up to a maximum of 20 seconds can be selected.
Workflows that depend on post functions being executed in a specific order can fail due to the asynchronous nature of Connect post-functions in Jira Cloud. One workaround is to delay the execution of a post-function, thereby creating a more predictable execution order. For example, on the approval of a Story you want to create sub-tasks and immediately transition them; in this case, you will have to delay the execution of the Transition Linked Issues post-function, so that the sub-tasks are created before they are transitioned. See the sample use case, below.
Where possible, it is recommended to use the Sequence of post-functions post-function or Shared action post-function to execute a series of post-functions in a specific sequence instead of applying a delay.
Need support? Create a request with our support team.
Copyright © 2005 - 2026 Appfire | All rights reserved.