This is feedback about task and stories

[Natalie Rudow]

I have used the tasks under stories for the past 3 years.  Why did you move to not linking tasks or sub-tasks to the story?  Such a lousy user experience requires the user to now link.  which conflicts with linking for dependencies vs. Hierarchy.  

A sad day for JIRA users.  

[Trudy Claspill]

Hello @Natalie Rudow 

Welcome to the Atlassian community.

For years now the default issue type hierarchy in Jira Cloud has been:

Epic (level 1)
|-- standard issues types like Story, Task, & Bug (level 0)
    |-- subtask issue types (level -1)

With a premium subscription you can modify that by adding levels above Level 1 and moving an issue type from level 0 to a higher level.

Only by moving the Story issue type to a level directly above the level containing Task could you have made a Task a child of a Story.

Subtasks can be children only of the issue types at Level 0.

There has not been any recent change to this functionality.

The Issue Type Hierarchy is a Global configuration. It is possible that the Jira Administrators for the Jira instance that you use have made a change to that configuration. But Atlassian has not change the way the product works.

As a user community we can can suggest ways that you can try to find out the root cause of the change in the Jira instance that you use. If you are not an administrator for that instance then part of our guidance may be that you talk to the people who are administrators for your instance.

Would you like to provide more information (steps to recreate, screen images) to help us understand the change you are observing so that we can offer you more guidance?