Update/Alert Main Ticket Assignee when linked Issues are closed

[Reb Bravo]

Hi Community,

We would like to create an automation that will alert the assignee (thru internal comment) every 2 hours once all linked issues are tagged as done. 

How can we make this possible for when we tried the automation we could not get the linked issues we have tried to use this JQL but still did not worked: 

issue in linkedIssues("", "is not empty") AND issueFunction in linkedIssuesOf("status = Closed")

We also have a legacy automation for this matter but it only updates through comment on the main ticket. What we want to achieve is for the automation to tag the assignee and several people so they can be alerted once the linked issues are all completed.

Hope we can hear from you soon.

Thank you and have a nice day ahead! 

Cheers,

Reb

[Andy Heinzer]

The legacy automation found on Jira Service Management site created before 30 August 2021 won't have the ability to do this.  That form of automation is considerably less feature rich when compared to the modern automation options.  I'd recommend using the new automation here instead.

[Vikrant Yadav]

Hi @Reb Bravo 

It seems that you are trying to create such automation when all linked issues moved to Done status, then issue with certain link type, like in my screenshot parent issue link type is blocks. 

When PAA-102,105, and 106 moved to Done then put comment on PAA-86 right and notify Assignee ?

[Reb Bravo]

Hi @Vikrant Yadav

Good day! Yes that is the idea but most of our linked issue is from other Projects which we are not an admin. So is it possible that we could not get the issue status from other projects due to lack of access?

Thank you!

[Vikrant Yadav]

@Reb Bravo  That's fine, you can apply this automation to multiple project. Create the automation rule in the project owned by you, once automation ready ask your Jira admin to map this automation with multiple project.s OR you can ask your Jira Admin to create automation for multiple project, Jira admin create automation rule and map with all the requested projects you want.  

[Reb Bravo]

Hi @Vikrant Yadav

Good day! I hope you are doing well. We are trying to improve the legacy automation for this for the automation suggested above does not work when the ticket linked to the parent issue is from another project. 

May we kindly know how we can tag the assignee in the comment using legacy automation?

We have tried to test several variables and non of it work. This variable [{{reporter.displayName}}|~accountid:{{reporter.accountId}}]! works fine in the automation but does not work on legacy. 

I hope you have some ideas on how we can make this possible thank you! 

[Vikrant Yadav]

@Reb Bravo  You can tag Assignee in comment using this smart value : 

[~accountid:{{issue.assignee.accountId}}]

[Reb Bravo]

Hi @Vikrant Yadav

Thank you for your feedback! We have already tested this and this only works on the new JIRA automation. May we kindly know if we can tag the assignee on the Legacy automation (old Jira automation)? 

[Vikrant Yadav]

@Reb Bravo  I am not sure about old automation. I can tag Bill who is expert in automation. 

@Bill Sheboy  can you please help us in creating automation ? 

[Bill Sheboy]

Hi @Reb Bravo and @Vikrant Yadav 

I do not have experience with the legacy automation and so have no suggestions for that feature.

Earlier in this thread, I note there was a challenge with accessing the linked issue status when it was in another project.  To do that, the rule will need to be multiple-project or global in scope, and your Jira Site Admin will need to configure such rules.

FYI: single-project scope rules can create or clone issues into other projects, but they cannot otherwise access or edit the issues.  (Except when using the REST API endpoints.)

Kind regards,
Bill