Show epic name instead of epic summary in board cards. Thanos Koulouris Jun 26, 2023. Recently we migrated all our projects to Jira Cloud, and noticed that issues belonging to an epic are not shown as they used to under Active Sprints and Backlog. The epic in each card used to be shown with its name. After migration, it is now shown with its 1 answer. If you want to add an issuetype like task,story etc to an epic there is a field called epic link.You can give the epic name/issue key in this field and it will automatically get added to epic. Excellent - Thank you!! Please accept the answer if it helped. Date ranges: Hover on an epic to view its date range. Drag its left and right edges to adjust the date range, or click the epic to open it and edit its details. Manage epics on the roadmap; Also, make sure that on Project settings > Issue types > Epic that the fields were added to the context fields. Regards, Angélica Confluence will then automatically generate a Jira Roadmap macro. ii) Use the macro shortcut menu: From the macro shortcuts menu in Confluence, simply select Jira Roadmap. iii) Pull up the macro menu: From the full macro menu in Confluence, select Jira Roadmap. Note: These steps are for Advanced Roadmap. How to Convert Epic to a Story - Jira Tutorial 2021Hey guys, In this tutorial, we will learn how to convert epic to a story in JIRA.--- What will be covered0 Clones the EPIC; Clones all sub tasks (in the initials task) Clones the taks and put the cloned key in the initial task in a free new field; Second automation. for updated new field in the initials task; update the new subtacks (not the initials, for me filtered by component) with the value of the new reference task; Third automation In Jira, Epic links aren't "normal" issue links so that's why your "linked issue match" doesn't match anything. You'll need to use the "JQL issues" drop down and enter: "Epic Link" = { {issue.key}} as the "Related issues JQL", before entering the appropriate statuses. (see image below) Hope that helps! Cheers, Mark C. 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 An epic is broken down into multiple stories, and is represented as an issue type in Jira. Stories - A story is a small body of work that represents a product requirement. Multiple stories can be used to make an epic. Sub-task - A sub-task is a unit of work contained within a story. It can be created to either split the issue into smaller Drag and drop the initiative issue type to the issue types for your project. Go to application settings, click Settings > Manage Apps > Advanced roadmaps for Jira > Hierarchy configuration. Click + Create Level and create the new initiative level. Make sure to map the initiative issue type to it. Click Save changes. yO0B2p.