Automation for 2 Standard issuetypes

[SAzaruddin.mp]

Hello Team,

I'm looking to set up an automation for two standard issue types, namely QA Task and Bug.

The requirement is that when a QA Task reaches its final status, which is "Done", I want the corresponding Bug issue to be automatically closed as well.

Could someone assist me with setting up this automation?

[John Funk]

Hi @SAzaruddin.mp 

Curious why you have a QA Task and a Bug for the same work. Why don't you just have a Bug issue type that goes through QA/Testing? 

Regardless, how are the two issues connected? 

[SAzaruddin.mp]

Hi @John Funk  

There are 2 different issue types, but we named as for our understanding.

Basically, QA Task is created in Manage Engine service desk under Jira project, after that our testing team will be notified the issue then they will create Bug in Jira under the same project so once the QA task is completed it will automatically close the bug too

Thanks, 

Azaruddin

[John Funk]

How are the issues related in the system then? 

[Valerie Knapp]

Hi @SAzaruddin.mp , thanks for your question.

You could modify this rule https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/140671/25000986  in the Branch, instead of updating the children of the trigger issue, to update the linked issues, in this case, of Bugs.

Please test this and share your feedback.

Cheers

[Ben Finn]

Hi @SAzaruddin.mp 

I think @Valerie Knapp has a great solution but wanted to throw my two cents in.

You could create an automation so that whenever a bug is created a QA task is automatically created. If you have them both be under an epic then you can set it so that when that epic is closed, all tasks underneath it should be closed as well (and vice versa).

Another alternative would be to have the QA task that's created be a subtask type rather than its own separate issue type. That way the QA task will be inherently part of the bug.