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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

when story is moved to cancelled, cancel all open subtasks

I have a created a Jira Automation rule to achieve  when story is moved to cancelled, cancel all open subtasks. However, i am facing 2 challenges:


1. Out of 'N' Sub-tasks tagged to a story if atleast 1 of them is in done state ,when i move my parent story to cancelled all sub-tasks attached move to cancelled but not the one which is already in DONE state 


2. When i move back my story from cancelled to other transition state then the sub-tasks are still in cancelled state as rule was applied earlier.

5 answers

5 accepted

1 vote
Answer accepted
Tom Lister Community Leader Dec 05, 2022

Hi @CK 

You need to check if your workflow has a route from Done to Cancelled in order for the automation to process those sub-tasks.

When you move a Story out of Cancelled , you will need to create the automations necessary to process the sub-tasks back to a desired state.

0 votes
Answer accepted

Thanks everyone. This solution is perfect but our org doesnt allow to change the workflow so we kind of deferred this request

0 votes
Answer accepted

Unfortunately our org is not allowing any work flow changes only for respective project. This automation iam enabling only for 1 project out of 100s 

0 votes
Answer accepted

@CK is it possible to share a snapshot of the rule configuration?

0 votes
Answer accepted
Mark Segall Community Leader Dec 05, 2022

Hi @CK 

Are you saying these two challenges are what is currently happening or what you want to have happen?

These 2 challeneges currently happening. How to overcome this ?

Mark Segall Community Leader Dec 05, 2022

Can you please share a screenshot of your rule as it stands today?

@CK - Just as a remark: You've to make sure that the workflow supports the transitions you configured. If it is not possible to transition from DONE to cancelled in the workflow, the automation can also not perform this change.  

Like Mark Segall likes this

Suggest an answer

Log in or Sign up to answer