Modifying trigger issue based on linked issue status

john_monteith
Contributor
February 4, 2025

I am trying to create an automation rule that does the following:

When a Problem Report issue type is selected for transition from status Implementation to status Verification, the rule will check if there are any linked issues of the type Change Request. If one or more are present the rule will check if any of these Change Request issues are not in Closed status. If there are still Change Request issues that are not closed a comment will be entered on the Problem Report issue stating that there are still open Change Requests, and the Problem Report will be transitioned back to Implementation. I'm missing how to affect the Problem Report issue as the comment gets logged in the "linked" Change Request issue and of course that issue cannot transition back to Implementation because that is not a valid Change Request transition.  Here is what my rule looks like, as you can see I've tried using Lookup Issue to switch back to the "trigger" issue.

 

A09 capture.PNG

1 answer

0 votes
Akash Singh
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 4, 2025

@john_monteith

It seems you’re trying to edit the trigger issue from within a branch, which isn’t allowed by design in Jira Automation. Your current implementation attempts to transition the Change Request to the "Implementation" status by finding a linked Change Request for the trigger Problem Report issue that is still open.

A more straightforward approach would be to skip the branch entirely and use a "Related issues condition". Here's how you can do this:

  1. Add a Related issues condition to your rule.
  2. In the Related issues field, select Linked issues.
  3. In the Condition field, choose Some match specified JQL.
  4. Use a JQL query to filter for open Change Requests. For example:
    issuetype = "Change Request" AND status not in ("Closed")

This will allow the rule to directly check for open linked Change Requests without needing a branch. Below is an example screenshot to guide you.

condition1.png

This approach simplifies the rule and ensures it works as expected. Let me know if you have further questions!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events