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?
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.
Due to recent challenges of most companies having to move to virtual and remote PI planning events, the Jira Align Solutions Architects wanted to start to capture some best practices and FAQ Table of...
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