Transition issue(s)
A workflow post-function that triggers a transition on the current issue or issue related to the current issue. This can be used to move an issue one step further in the workflow.
To add the 'Transition current issue' post-function to a transition :
Click Edit for the workflow that has the transition you wish to add the post-function on.
In the Workflow Designer, select the transition.
Click on
Post Functions
in the properties panel.Click on
Add
post function
.Select
Transition current issue
from the list of post-functions.Click on
Add
to add the post-function on the transition.Select the “Target issue” (see below)
Specify transition(s) either in the table or as a result of the calculated Nunjucks template. See Transition(s), below, for more information.
Click on
Add
to 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 document.
JMWE shows an error message on the issue view if any error occurs during the execution of the post-function. This message is only displayed if the current user is a Jira administrator.
When you add this post-function to a transition and trigger the transition, the add-on will transition the target issues using the specified transition, assuming it is valid for the current status and available to the current or selected user.
Issue(s) to operate on
Select the issues to be transitioned. They can be:
Current issue: Select this option to transition the current issue. This is the default option.
Sub-tasks of the current issue: Select this option to transition the sub-tasks of the current issue
Parent issue of the current sub-task: Select this option to transition the parent of the current issue
Issues that belong to the current issue (Epic): Select this option to transition the issues that belong to the current Epic
Epic of the current issue: Select this option to transition the Epic of the current issue
Child issues of the current issue in the Portfolio hierarchy: Select this option to transition the child issues of the current issue in the Portfolio hierarchy
Parent issue of the current issue in the Portfolio hierarchy: Select this option to transition the parent issue of the current issue in the Portfolio hierarchy
Issues linked to the current issue through any link type: Select this option to transition all issues linked to the current issue
Issues linked to the current issue through the following link type: Select this option to transition the linked issues of a specific link type. Select the specific link type under “Issue link”
Issues returned by the following Nunjucks template: Select this option to transition the issues returned by the result of a Nunjucks template. Input a Nunjucks template which is a comma-separated list of valid issue keys. For example:
"TEST-1"
"TEST-1","TEST-2"
{{ issue.fields.parent.key }}
{{ issue.fields.subtasks | join(",", "key") }}
Issues returned by a JQL search: Select this option to transition the issues returned by the result of a JQL search. Input a JQL search expression. For example:
project = TEST
returns issues of the project with the key TESTproject = {{ issue.fields.project.key }} and assignee = {{currentUser._accountId}}
returns issues of a project that belong to the project with key TEST and the assignee is the current user{% if issue.fields.assignee %} assignee = {{issue.fields.assignee._accountId}} {% else %} issuekey=INVALID-1 {% endif %}
Note that the {% if %} block is necessary to avoid an invalid JQL query when the issue is unassigned. In that case, the template will return a valid JQL query that returns no issue (
issuekey=INVALID-1
).
Transition(s)
Trigger one of the following transitions
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:
Click on Transition picker
Choose a workflow from Workflow name
Select a transition from the list of transitions displayed
Finally, click on either
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.
Click on Add.
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
Trigger a calculated transition
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: