Post-function "Break issue link" is aimed to make it possible for a workflow transition to selectively break issue links with current issue, or with any pair of issues in a Jira instance. Issue selection can be done by JQL query or comma separated issue keys in a field.
In the following example we configure the post-function for breaking "is blocked by" issue links of current issue to Improvement or New Feature issues, in statuses Open, In Progress or Reopened with Trivial or Minor priorities, and Due Date greater (later) than current issue's Due Date:
Note that:
Once configured, post-function looks like this:
We use JQL queries for selecting issues. The syntax is the same used by Jira for advanced issue searching.
You can insert field codes with format %{nnnnn} in your JQL query. These field codes will be replaced with the values of the corresponding fields in current issue at execution time, and the resulting JQL query will be processed by Jira JQL Parser. This way you can write dynamic JQL queries that depend on values of fields of current issue.
Example: issuetype = "%{00014}" AND project = "%{00018}"
will return issues in same project and with same issue type as current issue.
When you write your JQL for selecting the issues, take into account the following advices:
summary ~ "%{00021}"
will return issues with current user's full name. As full name can contain spaces, we have written the field code between double quotes. issuekey in ("%{00061}")
will be rendered in runtime like issuekey in ("CRM-1, HR-2, HR-3"), which is syntactically incorrect. On the other hand, JQL Query: issuekey in (%{00061})
will be rendered in runtime like issuekey in (CRM-1, HR-2, HR-3), which is correct.