That being said, the Epic Name field can not be retrieved on the child issues directly, however, you can create another custom field and use Jira automation to properly copy the "Epic name" value from the related epic to the child's custom field. As a practical example, you can check the automation rule below: The parameter { {issue.epic Stories, also called “user stories,” are short requirements or requests written from the perspective of an end user. Epics are large bodies of work that can be broken down into a number of smaller tasks (called stories). Initiatives are collections of epics that drive toward a common goal. query1: Project = xyz and issuetype in (Task) and "Epic Link" is not empty AND labels != epic-name-in-summary . But if i use query2: Project = xyz and issuetype in (Task) and "Epic Link" is not empty AND labels = PROD then it give one issue with label as PROD. Ideally query1 should also give result with labels name as PROD. That will give you the option to select a different Epic parent or unlink the issue from any parent. 2. In the Backlog screen expose the Epics panel. Drag and drop the issue from the issue list on the right onto a different Epic of the "Issues without epic" section of the Epics panel. (This works in Company Managed projects also.) 2 votes. Carlos Garcia Navarro. Community Leader. Sep 10, 2022 • edited. Hi @haeryn_kim , Yes. This other post may be helpful: At this point it's not a "create" it's more of a "move" existing tasks under the existing user stories under the Epic. With this default hierarchy you can't make an issue a "child" of another issue at the same level. So in this case you couldn't make a Task a "child" (under) a Story. You would have to convert the Task to a Sub-task, and then If you just want to move a couple of tickets, you can change the issue type directly: In Team-managed project, select the Move option from the Actions menu, once you select the sub-task issue type, it will let you map it to the new parent issue. In Company-managed project, you'll have the option to " Convert to sub-task ". 1 - Create the new Epic you want to move your issues to. 2 - Navigate to your issue navigator and create a filter to return all the issues from the Epic you would like to move the issues from, using the Epic link field. Then, click on the three dots menu > Bulk update issues: 3 - Click to Edit issues > change Epic link, moving it to the Epic .

jira change epic to task