In late 2022 the above changes will apply to the parent-link field as well. In 2023 we will convert all existing saved JQL and issue searches containing epic-link and parent-link to parent. Search results will not be affected* and no user action will be required. More specific dates will be added here as we get closer to the update.

The following screenshot shows how to convert the issue into a sub-task. Click on Next. If the status of the issue is not an allowed status for the new issue type. Select – New Status will be displayed. Select a new status and click on the Next button. Update Fields screen will be prompted to enter any additional fields, if they are required.

Issues at that standard level can have sub-tasks, but they can not contain issues at the same level. The "epic link" field makes it look like the Epic contains the stories, but it's not a parent/child relationship like issue-subtask is. To create an issue in an Epic in the main JIRA UI, create it via the usual "create issue" and fill in the

Epic workflows is a combination of tooling and processes. Epic generally have a different workflow then story. Epics are assigned to POs and they move the Epics based on the progress of stories by the various development teams. An epic can have easily upto 20 stories. You can also automate part of Epic workflows based on workflow statuses of

. 45 122 330 257 308 16 339 313

jira convert epic to task