When you add this post-function to a transition and trigger the transition, the add-on will trigger the specified transition on each issue linked to the current issue through the selected link type, assuming that transition is valid for the linked issue's current status, and it is available to the current or the specified user.
Input the transition name(s)
or id(s)
and optionally the workflow name manually or using the Transition picker. If you do not specify the workflow name (manually) the app will not check for a specific workflow. The app triggers the first transition specified in the table that is applicable to the issue in context.
To pick a transition using the Transition picker:
Use Transition Name
- recommended if you want the post-function to search for the transition to trigger by name, which is useful when targeting multiple workflows.Use Transition ID
- if you want to differentiate between transitions that bear the same name.To remove a transition: Click on the Remove
link for the specific transition
To reorder transitions: Select and move the transition in the table to reorder the list
Input a Nunjucks template that returns one or more transition name(s)
or id(s)
and optionally the workflow name. To specify a workflow name, write a Nunjucks template that returns the transition name
or ID
along with the workflow name separated by @@.
For example: Done@@HR workflow
.
To return multiple transitions, write a Nunjucks template that returns transition names
or IDs
each on a separate line. For example:
2@@Default Jira Workflow Done@@Another workflow Close |
Example of a template returning transition name:
{%if issue.fields.priority.name == "Blocker"%} Escalate {% else %} Assign {% endif %} |
Run As
The current user will be the author of the transition triggered by the post-function.
The add-on user will be the author of the transition triggered by the post-function.
Any user selected in this field will be the author of the transition triggered by the post-function.
Transition screen
If the transition uses a transition screen you might want/need to provide a value for fields (such as Resolution) present on the screen. Look below to know how to add/set/remove fields.
Add.
Remove
to remove a field.2.0
in the value box.Likewise, you might also want to provide a comment during that transition. This will only work if the triggered transition is associated with a transition screen.
Comment
can be any simple text, e.g. This is a comment
.
You can also use Nunjucks annotations in the comment using variables. To find out more about the variables, see How to insert information using Nunjucks annotations.Restrict to Group : Restricts the visibility of the comment to a specified group. When you select a valid group name in the Restrict to Group
field, the comment will be visible only to the members of the specified group. For no restriction, leave the field blank.
Restrict to Project Role
field, the comment will be visible only to the members of the selected project role. For no restriction, leave the field blank.Conditional execution
To execute this post-function based on the result of a Nunjucks template see Conditional execution.
Delayed execution
To delay the execution of this post-function see Delayed execution.
The options Run as add-on user and Run as this user are useful if the current user doesn't have the permission to transition the linked issue(s). |
The transition can be specified by name so that the transition can be found regardless of each linked issue's actual workflow, or by ID if disambiguation is required. |
Note that you can use this function to transition:
|