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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Automation Rule to transition Parent issue when related children issues, which are not in the same p

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!


1 answer

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.

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.

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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

7,121 views 8 28
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you