Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

automate movement on subtasks

I work with two boards. One Epic/story-level where the PO move the tasks from "Idea", "Backlog", "Ready", "In Process", "Done", "Rejected", "MayBeForTheFuture".

And another board where I only show "Ready", "In Developement", "Reviewing", "Done", "Rejected".

Ready and Rejected are mapped to the same, and "in developement" and "reviewing" are maped to "In Process" in the first table.

All issues follow all the steps in the workflow (idea, BL, ready, in dev, review , done, rejected) 

What I need is a way to ensure that when the PO move an story from column to column, All the sub-tasks move with it. From Backlog to Ready or from Rejected to Future.

Also, when all sub-tasks move from review to done, I'd like to have the story in the PO board moving automatically from "In Progress" to "Done".


Is there a way to automate those things ?? 

1 answer

0 votes

Hello Javier,

Thank you for raising this question.

JIRA Core does not have a functionality to automatically transition sub-task issues when its parent is transitioned, however, there are some add-ons that give you this feature.

I recommend you to try Automation lite for JIRA and configure automation rules like the example below:

Screen Shot 2019-03-08 at 15.40.33.png

This add-on has 300 free executions per month, so please let us know if it would meet your requirements or let us know if you would like to try other options.

Have a nice weekend!

When I create the rule is says that the branch for sub-tasks is a PRO feature and will be dissabled in withing 30 days.. Not X executions per monht.. Could it be that they changed the free-method ? 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

315 views 9 7
Read article

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