Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here.
To add the 'Unlink issues from the 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 Post Functionsin the properties panel.
Click Add post function.
Select Unlink issues from the current issue from the list of post-functions.
Click Add to add the post-function on the transition.
Add a Groovy condition in the
Condition.Click
Addto 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.
Issues to unlink
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 typelinkedIssue.get("status").getName() == "Rejected"returnstruefor all linked issues that are in theRejectedstatus.
Customize this post-function using the additional options provided as part of the post-function. The options are:
Run As
Select which user account will be used when running the post-function.
Run as user
Current user - The user who triggered the transition.
Specific user - Select a specific user account to execute the post-function.
User in field - Select a User Picker field or other custom field containing user values.
User from script - Enter a Groovy script that returns a user ID.
Examples:"jdoe"- To use a static value username.issue.get("assignee")- To return the current issue's Assignee.
Note: Prior to JMWE 8.4.0, this configuration stores a username value. If an Administrator changes a user’s username, the post-function will fail.
Existing post-functions created before version 8.4.0 should be updated; open the post-function for editing and save it (no changes are necessary). This will update the configuration to use the immutable user ID value.
New post-functions do not need to be updated.
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.