This type of board gives leaders an overview of the progress on each epic and user story. However, the board is impractical for the development team. The development team needs to plan and execute sprints to work on the tasks that are required for each user story. These tasks are only visible as links on this board. By using our Great Gadgets app you can do the grouping in dashboard gadgets. For example, the Team Wall board gadget can display swim-lanes by epics. This is how the gadget looks like (the colors can be customized). In addition, the Work Breakdown Structure (WBS) gadget can group the issues by their hierarchy Epic > Story, Task > Subtasks. Jira cloud. Diagnosis. The field 'Epic Link' on the child issue should be matched with the 'Epic Name' from its parent, but this mapping is not directly supported under Automation action. The available options are Copy from issue/Copy from parent/ Copy from Epic/ Copy from trigger issue, but these options are only for 'Epic link' not 'Epic Name'. Plain Jira's hierarchy is. Issue (Story) -> Sub-task. If you add Software, it gives you. Epic -> Issue (Story) -> Sub-task. Advanced Roadmaps (nee Portfolio) adds themes and initiatives above that. Jira Align gives you a hierarchy right the way up through SAFe (and other agile at scale frameworks). Then there are non-Atlassian apps you can add 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. Answer accepted. You have nothing wrong. Sub-tasks are a part of their parent issue, not separate items, and you can always state that "sub-task X is part of issue Y, which is in Epic Z, so, X is a part of Epic Z". While Jira is good at enforcing the right structure, it's really bad at reporting on it. A sub-task is always part of an Epic when I am new to JIRA and Kanban. I was expecting that when I create an epic and link some stories and tasks to it. The status of the epic will automatically change (e.g. to done) when all the stories and tasks linked to it are done. But it seems this is not the case. Ah, I see! That is not the way to convert a subtask type issue to a base level type issue. The hierarchy of issues is. Epics |-- base level type issues (Story, Bug, and usually one named Task) | subtask type issues (one by default named Sub-task) You can add more issue types with different names at the base level and the subtask level. q1q4.

jira convert epic to task