Unable to see Sub-Tasks anymore on my Jira Stories

[Sam Hammond]

As per Jira's new policy Epic → Story/Task → Sub-task is also not working for me since you roll-out this big change. It disrupted how we were managing the issues in our organization. We were previously creating sub-tasks under stories but now we are unable to do so. So i created an epic and tried to add a story under that but i am also not able to add story under and epic either now. Like i just want to add a sub-task under a story as story being the parent. But i am unable to do so now. Attaching my workflow hierarchy. Please tell me what to do and it's really urgent and important for me being a Scrum master and Project Lead my work is affected by this change.

You can see in the photos that i am unable to link my story to my epic or my sub-task to my story.

[Ryan M]

Story should be a standard work type, the same level as task (level 0). You've moved it in the hierarchy to be level 3 in your hierarchy for some reason (this is nothing to do with atlassians changes), which is not where it should be. A work type thats higher in the hierarchy than another, cannot be its child (this is the point of hierarchy).

I assume by your question that this was not intentional, and if you want this to function as expected in a default setup, you would need to move Story back to the task level (level 0) in the hierarchy.

I'm not sure what other configuration items may have been tied to this change and might also need to be reviewed. If people have already been utilizing stories in this hierarchy, that will break/orphan any children of stories under level 3 in the hierarchy, so if it's been used much.... it might be a bit of a mess to clean up. I would recommend you would want to test your cleanup in recently updated sandbox first and have some UAT testers to make sure it doesn't affect anything important, because the effects of that change cannot be undone.