JMWE Cloud: Work only on newly linked issues

Summary

In Jira Cloud, linked issues do not support history-based JQL changes directly within transition post functions. This article provides a workaround using JQL to identify issues linked during the current transition by filtering for recently updated issues. This covers two scenarios: targeting all recently linked issues and targeting recently linked issues of a specific link type.

Problem

When linking issues to a parent issue during a transition, JMWE post functions (such as "Set issue fields") typically offer to run on all child issues or all issues linked through selected link types. However, if you only want to execute an action on the issues newly linked during that specific transition—and ignore existing links—there is no native "history" filter for links.

Cause

Jira Cloud's JQL and the linkedIssues filter do not natively track the "date linked" as a searchable history field. However, the act of linking an issue triggers an "Updated" event on that issue.

Solution

You can use the Target issue(s) configuration with a JQL expression that filters for issues linked to the current issue that were updated within the last minute.

You can use a JQL filter the linked issues:

1. In your post-function configuration, under Target issue(s), select Issues returned by the following JQL search.

2. Enter the following JQL:

• How it works: This JQL finds all issues linked to the triggering issue ({{issue.fields.issuekey}}) that have been updated in the last minute. Since linking an issue counts as an update, only the newly linked issues will match.

Use Case 2: Target recently linked issues by Link Type

Use this expression if you only want to target specific link types (e.g., "Blocks") that were added during the transition.

1. In your post-function configuration, under Target issue(s), select Issues returned by the following JQL search.

2. Enter the following JQL (replacing "Blocks" with your specific link name):