how can I update the status of an issue when all related issues change status

[Deleted user]

I try to explain hoping to make myself understood. As you can see from the image I have a BigPicture program that uses a dependency relationship built using custom issue links. The hierarchy is Area, Activity, Project, Sub Project.

In this moment I put two automation rules, the first rule changes state of an issue when the triangle cursor is used at the bottom of each issue, if it is moved the issue goes in progress. If it is moved to the end the issue becomes "done", if it is at the beginning the issue is ToDo.

Then I put a rule that brings an issue in progress if it is connected with another issue of the dependent ones. For example, when I add an Area issue and then add an Activity issue and link the Activity issue as a child of Area using the appropriate issue link, the Area issue changes from ToDo to In Progress if it was in ToDo or Done.

Now I don't really know how to handle the problem I would like to make sure that a parent issue is put to Done when all the child issues are done.

[Petter Gonçalves]

Hello @[deleted]

Thank you for reaching out.

Per your description, I understand you are trying to sync the status of your parent issues with their related child issues, updating the parent status to Done when all their related child issues are done. Is that correct?

Indeed, it is possible to achieve this goal by using the Related issues condition, as explaining in the documentation below:

Synchronize parent and sub-task issues with Automation for JIRA 

In your specific scenario, this would be the rule:

Let us know if you have any questions.

[Deleted user]

@Petter Gonçalves 

I want to thank you for taking my call. Yes, I read that page that explains the related issues. But maybe I didn't read it well so I didn't know how to make it work properly. So you tell me that it's better to make three rules one for each type of issue that I have to manage and then they should work in waterfall? Today I'm going to try and comment on this topic. Thank you.

[Petter Gonçalves]

You are welcome @[deleted]

Yes, I believe the best scenario here would be to use three different rules in waterfall to better organize the automation itself.

Let us know if something does not work as expected.

[Deleted user]

@Petter Gonçalves 

I've done other tests, and now I'm in this situation. I'll explain. I have this structure: issuetype Project that can have one or more issuetype Sub-Project connected with the relationship "is project of" (if I look at the issue Sub-Project) or is "under project of" if I look at the parent issue, say, that Project that has one or more sub-projects linked precisely.

I want to use automation so that every time a status change event is captured to "done" I check if the issue that has changed is a sub-project issue and then I want to go back to its parent issue, the project issue, and then check if all the sub-project issues related to the project issue are in done status.

I hope I was able to explain clearly. I can't build this query with automation for Jira and JQL (p.s. if needed I also have Script Runner, but I can use it less well than automation for Jira).