Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,558,797
Community Members
 
Community Events
184
Community Groups

JIRA AUTOMATION- Transition issue when its subtasks and any linked issues are transitioned to closed

Edited

I would like an issue to be transitioned when all of its subtasks and any linked issues are transitioned to closed.

linked issues will always be using the same link value.

I've tried a number of things. I even installed Scriptrunner but alas no cigar.

This must be achievable.

Any help would be greatly appreciated

2 answers

1 accepted

3 votes
Answer accepted
Walter Buggenhout _ACA IT_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 06, 2023

Hi @Darren.Fairweather 

You should be able to pull this off using a rule like this:

Screenshot 2023-04-06 at 13.25.10.png

Trigger the rule when a sub-task transitions to closed (the example is based on the template library and statuses / conditions do not match your use case 100%, but the essential pieces are there).

You may want to add a condition in the beginning to see if your trigger issue is a sub-task.

You can create a second rule for standard issue types (i.e. issues that are not sub-tasks) and replace the For Parent branch with a For linked issues branch using more or less the same logic.

Hope this helps!

@Walter Buggenhout _ACA IT_ Legend! I have a feeling we will be talking again soon. Thanks you very much!

Walter Buggenhout _ACA IT_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 06, 2023

😅

Like Darren.Fairweather likes this

Hi @Walter Buggenhout _ACA IT_  - Got an issue buddy! If i close the linked issue last nothing happens (not even registered on automation audit log. Where as if a close the sub tasks last the automation works. Any thoughts? Thanks in advance

@Walter Buggenhout _ACA IT_  yeah its does not like the linked match.

 

Error searching for related issues. This is most likely because the following issues don't have a related issue of the type you specified. Try narrowing your search to only include issues that contain links to related issues:
NTT-29774: "(((key = ) AND (issuetype = Onboarding and Status = "Build / Configuration")) AND (key != NTT-29774)) AND (project in (10064,10001,10037))" - Error in JQL Query: Expecting either a value, list or function but got ')'. You must surround ')' in quotation marks to use it as a value. (line 1, character 10)

As you say seems like i need two rules. One using parent for subtasks and one "for linked issues". Trouble is i only want the automation to trigger when sub tasks and issuelinks are complete and not being able to add both in the same rule using an "and" scuppers that? 

Suggest an answer

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

Atlassian Community Events