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,463,057
Community Members
 
Community Events
176
Community Groups

Roll up of State updates from child to parent

In my testing I've seen updates to State at the Task level auto roll up and update the State of the Task's associated Story, but I don't see this happening on the roll up from Story to Feature and from Feature to Epic.

Does anyone know of any definitive documentation about State behavior's impact on it's parent object?

thank you!

K

Kelley Cooper

1 answer

1 accepted

2 votes
Answer accepted

 Hi @Kelley Cooper,

I assume by your question that you are referring to when a sub-task on a story in Jira is started that the story moves from Ready to Start to In Progress in JiraAlign.

This same behavior is standard for features and portfolio epics in Jira Align, assuming all integration setting are correct in the connector. So, assuming a stand-alone Jira Align install (or a properly configured integration with Jira) the moment an agile task (Jira sub-task) under a story is moved from Ready to Start to In Progress, the parent story will move to In Progress, then the parent feature will move to In Progress, then the parent portfolio epic will move to In Progress (all in Jira Align) .

When the workflows aren't mapped properly between Jira and Jira Align you can run into a situation where Jira overrides Jira Align and resets the feature (Jira epic) back to Ready to Start from In Progress. To confirm this is the issue, check the audit log on one of the features in Jira Align.

Regards,

Peter

@Peter Jessen is correct; the audit log will reflect these state roll-ups when they take place.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events