Jira Automation to Resolve an Issue

Elif Alverson
Contributor
July 20, 2022

Hello,

Project X has an automation called "New Hardware". When there is a "New Hardware" issue is created, it automatically creates two issues linked to it in two different projects with the similar name. (Let's say Project Y and Z) We would like to have automation to resolve the Project X "New Hardware" issue type whenever the linked Project Y and Z issues both are resolved. How can I do this with the Jira-Automations? Any help will be appreciated. Thank you.

2 answers

1 accepted

1 vote
Answer accepted
Stefan Salzl
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 20, 2022

Hi @Elif Alverson ,

how are the issues linked? To know the link type would be good in order to find  the right solution (as this depends on wheter check the source or destination issue)

Best
Stefan

Elif Alverson
Contributor
July 21, 2022

When Project X - New Hardware issue is created, it creates Project Y- New Hardware (Y) and Project Z- New Hardware (Z) issues. Project X - New Hardware issues is blocked by Project Y- New Hardware (Y) and Project Z- New Hardware (Z) issues. Does that answer your question? Elif

Like Stefan Salzl likes this
Stefan Salzl
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 22, 2022

Hi @Elif Alverson ,

thanks for the information. that was really helpful.

Please see the screenshot below. I just created it within 1 project and with other status. With some changes (scope needs to be multi-project to cover project X, Y and Z as well as your status) this should do the work:

image.png

Hope this was helpful and looking forward to your feedback.

Best
Stefan

Like Elif Alverson likes this
Stefan Salzl
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 22, 2022

Hi @Elif Alverson ,

in case this was helpful and solves your problem please consider to mark the answer as accepted in order to help other users to find the correct answer in case they are faced with similar problems.

Best
Stefan

Elif Alverson
Contributor
July 22, 2022

Hello @Stefan Salzl ,Thank you so much for your help.

Unfortunately this solution above does not work the way we would like. As you see the first step is checking WHEN the parent ticket is transitioned to done. We would like the parent ticket's status change to done when the linked tickets are done. 

 

Thank you.

Stefan Salzl
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 22, 2022

uuuuh.....thanks for the hint @Elif Alverson . There was is a mistake in my screenshot. The first transition action right after the trigger is wrong.... =S

furthermore:
no - the trigger doesn´t say anything about which issue is checked. It just listens for a transition of issues in the projects that are in scope of the rule details. You could further specify with a condition after the trigger to only go further when the transition happens in project y or z. It´s important to configure the rule as a multi-project or global rule. This can be done in the rule details:

image.png

 

From the screenshot below the project "ASDF" and "FT" would be your "Y" and "Z". So the following steps will only run when the transition of an issue happens in those projects.

 

image.png

Hope this clears things up a little bit. If I got the requirement wrong please let me know where.

Best
Stefan

Like Elif Alverson likes this
Elif Alverson
Contributor
July 22, 2022

@Stefan Salzl , thank you! I created a similar automation and it worked. 

You are awesome!

Like Stefan Salzl likes this
Stefan Salzl
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 22, 2022

 

Aaaaawesome @Elif Alverson !!!! Great work 👌🏼💪🏼 Good to know you got that working.

Best
Stefan

0 votes
Peter DeWitt
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 20, 2022

@Elif Alverson , hey this is a really interesting question. I can get you an automation that will closed the issue then a linked is is closed but I don't think there is a simple way to check when all other linked issues from a linked issue are closed.

1. Does one of the linked issues in Y or Z normally close last or are they random.

 

cheers -dewitt

Elif Alverson
Contributor
July 21, 2022

When Project X - New Hardware issue is created, it creates Project Y- New Hardware (Y) and Project Z- New Hardware (Z). So when the Project Y- New Hardware (Y) and Project Z- New Hardware (Z) issues are manually closed, we would like Project X - New Hardware issue is auto closed. Does that answer your question? 

Stefan Salzl
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 21, 2022

Hi @Elif Alverson ,

thanks for the information. that was really helpful.

Please see the screenshot below. I just created it within 1 project and with other status. With some changes (scope needs to be multi-project to cover project X, Y and Z as well as your status) this should do the work:

image.png

Hope this was helpful and looking forward to your feedback.

Best
Stefan

Like Elif Alverson likes this
Elif Alverson
Contributor
July 21, 2022

Thank you for your quick response. Where do you determine the issue type to be closed for Project X?

Thank you.

Peter DeWitt
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 21, 2022

It's going to be done by the issue link type. It won't matter what the actual issue type is. In Stefan's example, the automation is going to look at the issue linked by the blocks issue link. Whatever issue is on the other end, that's the one that will be closed.

Like Stefan Salzl likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events