Our new Appfire Documentation Space is now live!

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

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 32 Next »

A workflow post-function that triggers a transition on all issues linked to the current issue through a selected link type.

To add 'Transition linked issues' post-function to a transition : 

  1. Click Edit for the workflow that has the transition you wish to add 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 Transition linked issues from the list of post-functions.
  6. Click on Add to add the post-function on the transition.
  7. Input the transition name or ID in the Transition field. To use a dynamic (calculated) transition name or ID see, How to insert information using Nunjucks annotations
  8. Select the link from the Issue Link Type drop-down.
  9. Click on Add to add the post-function to the transition.
  10. 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:

Filter by label

There are no items with the selected labels at this time.

Specific to this post-function:

Filter by label

There are no items with the selected labels at this time.

Related links

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

Customize this post-function using the additional options provided as a part of the post-function. The options are:

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

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.

    • To add a field : Select a field from the list of fields and click on Add.
    • To Remove an added field : Click on Remove to remove a field.
    • To Set a field value : 
      • Copy value from current issue : Copies the field value(s) from the current issue.
      • 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 Fix Version/s to 2.0, you can specify 2.0 in the value box.

Likewise, you might also want to provide a comment during that transition.

    • Comment : adds a comment to each linked issue being transitioned. The 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.
    • 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 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 : Restricts the visibility of the comment to a selected project role. When you select a project role from the drop-down 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.
      • 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 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:

  • The parent issue of a sub-task by using the built-in is Subtask of link type and vice versa using the is Parent of link type
  • The Epic of an issue by using the built-in belongs to Epic link type and vice-versa using the is Epic of link type
  • No labels