You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The behavior described in this document is foundational to Jira Align, hence it can be noticed in both Standard and Enterprise editions, and it can’t be altered, regardless of having an active Jira Connector.
We aim to explain the Jira Align behavior where a parent's work item status changes automatically once any of its children's status is changed from 0-Pending Approval to
2-In Progress (or any status after).
Imagine you have the following scenario: A feature (e.g. Feature #1), linked to several stories (children work items).
All of them, including Feature #1, are in 0-Pending Approval state; so, in other words, no work has been started yet.
Once you move any story from 0-Pending Approval to 2-In Progress (or any status after), Jira Align triggers a status update that will change the parent work item status to
2-In Progress as well.
Since stories are considered small pieces of work of a feature, Jira Align understands that if you started a story, you started part of the whole planned workload (the feature), hence updating the parent work item’s status to reflect that the work has been initiated.
The same happens with tasks and stories, and features and capabilities/epics.
This behavior works in chain reaction, updating the parent's status all the way up to
2-In Progress (if they aren’t already in this state) from tasks to Epics