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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,459,191
Community Members
 
Community Events
176
Community Groups

Parent work item’s status changes upon children’s statuses updates

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.

Objective

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).

Description

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.

Gif_Auto_state.gif


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.

Notes

  • 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

 

 

1 comment

Is there a step by step guide on how to have this added to a project?

Thank you,

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events