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....
I cannot reproduce this, so I assume it is a bug specific to your configuration.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.