Automation based on linked issue updates

[Mark J]

Hello,

I want to know if this can be achievable with an automation.

IF my issue Clones another issue (project=B)
AND my issue.status !=Done

THEN IF the other issue status changes
              ADD comment on my issue:"Linked issue Status changed to @status"
ELSE IF the other issue comment is added
           ADD comment on my issue:"Linked issue Comment @Comment added"

The main problem I see is the trigger, to be based on changes on linked issue.

Thank you.

[Bill Sheboy · Accepted solution]

Hi @Mark J 

I am unclear what problem this scenario would be solving.  Perhaps if you clarify that it will help the community to offer better suggestions.  Thanks!

Until we know that...

From what you describe, I expect you will need multiple rules, and need to invert your thinking about the triggers, such as "when the issues transitions to a new status" (in this case, the linked one instead) use that information to branch to / update the original issue.

Kind regards,
Bill

[Mark J]

Hi @Bill Sheboy ,

Let's say Project B are incidents, and are cloning their issues to several other projects. One of them it's created for my team, Project A. After we provide a solution on our side, we have to wait the initial issue updates (maybe when is done, so we can close ours too  or extra comments added, meaning extra to-do tasks) 

As a mention, I only have admin for my project; can I set rules to check updates on linked issue, bur through my project issue?

Thank you for the reply.

[Bill Sheboy]

Thanks for clarifying, and the answer is you will need a global or multiple-project scope rule to do this.  Your Jira admin can help create such a rule in the global automation view / area, using their elevated permissions.

Project scope rules can create or clone issues into other projects.  But they cannot access them otherwise, such as to examine fields or update them.

A work-around is to instead call REST API issue functions with the Send Web Request action to access issues in another project from a project-scope rule.  However with the changes to the automation packaging model that is not worth the effort or rule complexity, in my opinion.