Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×Dear Community,
I want to create an automation rule that automatically closes (or else) the parent issue when the (last) child is resolved (e.g.). Problem is the children issues are spread through different Projects and I would like to have one rule in the parent issue's project.
We have use Automation Plugin.
Any help is appreciated!
Peter
This should be doable through a related issues condition/step. You can specify the query to not be looking for a specific project (so it doesn't care about which project the linked tickets are in). There are a number of Related Issues choices in this rule, one of them will work - worst case, you can use another JQL query there.
This can be done as part of a branching rule - where before this you're determining the Parent you want to be closing, and after you tell it to transition the parent to the status you want.
You'll want that JQL query ("matching JQL") to return the issues you're expecting for a few different tickets, you can use the Validate query link on the right to ensure you're seeing the expected number of children linked to the parent.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Chris,
thank you for your help and the given hints. Right now I am not sure where to put the rule itself. Should it be in the parent's project or in each project where possible related issues might be?
Sorry for my delayed responses. This rule is not my top prio but really nice to have.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No problem!
The rule itself can be housed either on the project, or you can make it a global rule and then just specify a project inside (this comes at the cost of a more complicated audit log).
I would suggest you set this for a single project (that's found in the rule details under SCOPE), and then you could change the scope to multiple or global later, depending on your needs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Great hint and will have to limit it a bit - audit log now superhuge. :-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.