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
Community Members
Community Events
Community Groups

Removing or adding an Epic as a parent to a Feature will change the Feature's Process Step/State


Is this behavior "as designed" for Jira Align or might this be a bug or a configuration matter?  If this is desired behavior, is there documentation to support it? 

I understand that this is not a common practice in managing our work. Generally we start with the Epic and build out it's Features, Stories etc. and there really shouldn't be the need to parent/un-parent a Feature. However, this does come up from time to time and it would be nice to know the expected behavior. 

2 answers

0 votes
Tina Behers Community Leader Jul 05, 2021

@Tracy Walton The only time I have seen that happen is when the process steps are different for Epics/Features across programs & portfolios. 

This happens, especially when you remove a parent epic and not have a "stand alone Feature". When this feature had a parent, it was using the Feature process steps.  When it becomes a stand alone feature, it uses the Epic process steps. 

I don't believe the documentation covers all of the"gotcha's" around stand alone features....

0 votes

I cannot reproduce this, so I assume it is a bug specific to your configuration.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Align

Rockin' the Roadmap - How to make most of the Roadmap with Jira Align

The roadmap challenge for large scale agile enterprises Regardless of the agile framework you use, the agile enterprise has a massive scale with the challenge to connect hundreds of teams and thous...

3,732 views 8 30
Read article

Atlassian Community Events