Our new Appfire Documentation Space is now live!

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

Unlink issues from the current issue

Owned by David Fischer
Last updated: Jun 16, 2022 by Richard Stone[Appfire] (Deactivated)
3 min read



Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here.

 

A post-function that will unlink issues from the current issue based on the result of a Groovy condition.

To add the 'Unlink issues from 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 Post Functionsin the properties panel.

  4. Click Add post function.

  5. Select Unlink issues from the current issue from the list of post-functions.

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

  7. Add a Groovy condition in the Condition.

  8. Click 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 checks the specified condition against each linked issue of the current issue, except the ones added on the transition screen, if any. If the condition evaluates to true or a Groovy truthy the issue will be unlinked. To include the issues linked on the transition screen, if any, move the post-function after the Update change history for an issue and store the issue in the database built-in post-function.

Condition 

Input a Groovy condition in Condition. You can test your condition using the Groovy script tester.

Examples:

  • linkTypeName == "Blocks" returns true for all linked issues that are linked to the current issue with "Blocks" link type

  • linkedIssue.get("status").getName() == "Rejected" returns true for all linked issues that are in the Rejected status.

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

Run As

Run as user: Select one of the following options to set the author of the action performed by this post-function as:

  • Current user: The user transitioning the issue.

  • Specific user: The user specified in the select-list provided. Start typing into the field to select a user from the list of auto-suggestions.

  • User in field: The user specified in a user picker field of the issue being transitioned. Select one of the user fields from the list of available options in the field provided.

  • User from script: The user returned by the Groovy script specified in Script. This script should return either the Username of the user or an ApplicationUser object.

    Examples:

    • "jdoe" - Username

    • issue.get("assignee") - the current issue's Assignee

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. On development and staging Jira instances, you can activate error reporting for all JMWE post-functions on the JMWE configuration page, and it is recommended to do so. But on 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.