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 19 Next »


A post-function that will link the current issue to all issues that satisfy a parameterized JQL query.

To add the 'Link issues to the current issue' 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 Link issues to the current issue from the list of post-functions.

  6. Click on Add to add the post-function on the transition.

  7. Add a JQL query in the JQL expression.
  8. Select the maximum number of issues in Max. Issues.
  9. Select the link type from the Issue Link drop-down.
  10. Click on Add to add the post-function to the transition.

Related links :

For information on where the post-function needs to be placed on a transition, see Placing post-functions on a transition.

Refer to the Use cases for post-functions page for use cases for this post-function.

When you add this post-function to a transition and trigger it, the add-on links the current issue to the specified number of issues that satisfy the specified parameterized JQL query.

  • JQL Expression: Input a JQL expression that returns the issues to link. You can include Groovy Template markup to your JQL expression and test using the JQL expression tester provided in this post-function.

Examples:

    • project = TEST returns the issues of the project whose key is TEST
    • assignee is EMPTY returns all the unassigned issues.
    • project = TP and assignee = <%= issue.get("reporter").getName() %> returns the issues of the project whose key is TP and the reporter is the assignee.

Note: If the current issue satisfies the specified JQL query, an error is logged because you cannot link an issue with itself.

You can find more information about searching for Jira issues using JQL here: Advanced searching and Search Jira like a boss with JQL.

  • Max. Issues: Input the maximum number of issues that the JQL expression should return. The value cannot be more than 50.

Link type

  • Issue Link: Select the link type to be created between the current issue and the issues returned from the JQL expression.

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

Run As

  • Run as user: Any user specified in this field will be the creator of the issue links.

Conditional execution

To execute this post-function based on the result of a Groovy expression see Conditional execution/validation using a Groovy expression. The condition is evaluated only after the JQL query runs and not before. It will be evaluated against each issue returned by the JQL query allowing you to further filter the issues to link to the current issue. The issues returned by the JQL query will be available in your Groovy script through the linkedIssue variable. 

Error Handling

By default, all errors (Java Exceptions) raised by this post-function, including those raised by custom Groovy scripts, will be logged in the JIRA log file but will not be reported to the user and will not prevent the transition from completing. However, when designing new workflows or troubleshooting them, it is more convenient to be notified immediately of any such error during the execution of the transition. For example on the production Jira instances you might want to show errors only for the post-function(s) being worked on, in order to avoid disrupting other workflows. To make errors raised by the current post-function prevent the transition from completing and show the error in the browser, select Make transition fail when an error occurs in this post-function.

If you want to show all the errors, either only to the admins or to all users, configure the option globally on the JMWE configuration page. For example, on development and staging Jira instances, you can activate error reporting for all JMWE post-functions, to display all the errors and it is recommended to do so, and on production Jira instances you might want to activate error reporting only to administrators so that they can be made aware of configuration errors.

When the option is selected on a post-function, it overrides the configuration on the JMWE configuration page.

  • No labels