Automation Using Feature=Story Hierarchy to Change Status on Feature When all Stories Done

Question

We are using Jira Data Center to manage a project using a Feature => Story => Task Hierarchy. I'd like to set up automation so that when all children (stories in this case) are all marked done by the agile team, then Jira will automatically change the status of the parent feature (in our case Validating on Stage is the next status in our ART kanban). Seen lots of variations on using Epics and even Stories with Tasks. Wonder if anyone else has experience doing this?

Trudy P Claspill · Answer

Thank you for sharing that screen image @Joe Fewell

In order to create an automation to change the status of a related issue, we have to fully understand how the related issues are connected. That informs our decision about which components we can use in the rule to shift the focus from the story that triggered the rule to its parent issue.

In this case I can see that the field Parent Link is showing the key UI-11838 as the parent of the story you're viewing - UI-13789. That does suggest that the extended issue type hierarchy is being used.

What version of Jira DC are you using? That will help us determine what functionality is available to you in the Automation feature. You can get that version information by clicking on the Help button near your avatar and then selecting About Jira.

Joe Fewell · Answer

Hi @Trudy P Claspill thank you for your note. We are using Data Center and I only have admin permissions for my project so I cannot directly get into the hierarchy config screen. I can share an example story detail view tho. If I need to get our org admin to give me a screen shot of our hierarchy, I can do that but it may take a little bit. Please let me know your thoughts. Thanks

Trudy P Claspill · Answer

Hello @Joe Fewell

Welcome to the Atlassian community.

I'm trying to get a better picture of the issue type hierarchy. Can you show us the Issue Type Hierarchy configuration screen and point out where the Feature, Story, and Task issue types are located in the levels?

Can you show us an example Story issue details view that shows the related parent Feature and related child Tasks? Obscure confidential data. I want to see how the Story shows the connection to the Feature and the Tasks.