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

Automation that Updates the current issue to done once subtasks and Linked issues are done?

Hi,

I am using a customized issue type, and I would like to know how can I build an automation that updates this issue once linked issues are done also to done.

1 answer

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 27, 2023

Hello @Bruno Xavier 

There is a difference between "linked" issues and subtasks. Are you concerned with both, or with just subtasks?

If you do want to consider linked issues, do you want to consider all linked issue, or only issue linked in a specific manner or from specific projects?

There are two basic methods this could be handled.

With one method, each time an issue is marked as "done" you find its parent (if it was a subtask), and/or its linked issues. Once you have that (the parent and/or linked issues) then you have to check if all the subtasks of that parent (or all issues linked to it) are "done". If they are, then you update the issue.

This could cause a large number of rule executions to occur, and there is a change to the limits and model for counting executions that is going into affect soon. You need to evaluate if the above method would cause you to hit those limits.

The second method is to create a Scheduled rule that selects the issues you would want to consider updating, and then checks all their subtasks and linked issues to see if those are done. This results in fewer rule executions, but there may be some delay between when all the subtasks/linked issues are done and when the issue you care about gets updated.

Other scenarios you should consider are:

- what if your issue has been manually set to done but a subtask or linked issue is not done?

- what if everything is set to done, but on a future date one of the subtasks or linked issues is reopened?

Suggest an answer

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

Atlassian Community Events