You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
@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....