A workflow post-function that triggers a transition on the current issue. This can be used to move the current 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 Functionsin the properties panel.Click on
Addpost function.Select
Transition current issuefrom the list of post-functions.Click on
Addto add the post-function on the transition..png?version=1&modificationDate=1501143362078&cacheVersion=1&api=v2&width=312&height=378)
Specify transition(s) either in the table or as a result of the calculated Nunjucks template. See below for more information.
Click on
Addto 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.
Known limitations common to all post-functions:
For information on where the post-function needs to be placed on a transition, see Placing post-functions in a transition.
Refer to the Use cases for the post-functions page for use cases for this post-function.
Refer the Troubleshooting and Support page if the post-functions does not seem to be working as you would expect.
When you add this post-function to a transition and trigger the transition, the add-on will transition the issue further using the specified transition, assuming it is valid for the new status and available to the current or selected user.
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:
{%if issue.fields.priority.name == "Blocker"%}
Escalate
{% else %}
Assign
{% endif %}
Run As
Run as current user
The current user will be the author of the transition triggered by the post-function.
Run as add-on user
The add-on user will be the author of the transition triggered by the post-function.
Run as this user
The 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.
To add a field : Select a field from the list of fields and click on
Add.To Remove an added field : Click on
Removeto remove a field.To Set a field value :
Set field value to : You can set the field to a specific value, wherein the value can also include Nunjucks annotations.
For example: To set the Assignee to Charlie, you can specify theaccountId(use Lookup user feature to know the accountId) of user Charlie 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 : adds a comment to the current issue. The
Commentcan 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.Comment visibility :
Restrict to Group : Restricts the visibility of the comment to a specified group. When you select a valid group name in the
Restrict to Groupfield, the comment will be visible only to the members of the specified group. For no restriction, leave the field blank.Restrict to Project Role : Restricts the visibility of the comment to a selected project role. When you select a project role from the drop-down
Restrict to Project Rolefield, the comment will be visible only to the members of the selected project role. For no restriction, leave the field blank.Restrict to Internal (Jira Service Desk only) : Restricts the visibility of the comment to the Service Desk Agents and Collaborators only.
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 Run as add-on user and Run as this user options are useful if the current user doesn't have the permission to trigger the specified transition on the current issue.
Also, note that the specified transition can be hidden from users using the Hide Transition condition.