Let's first align a few common aspects of a sub-task: Are small. Do not deliver value by itself. Are oftentimes used as a means to assign "parts" to different people and to break down problems into different activities. The decision on whether sub-tasks are required or not should be taken by the team working on them. Start with an existing epic. Create a CSV for a single issue that you wish to associate to that epic. Use parent as the field and put in the epic issueKey, e.g. Abc-123. when mapping the field, be sure to map your parent CSV column to the Parent field. Like • João de Sousa Crespo likes this. as @Fazila Ashraf mentioned, you can have more than 3 levels of hierarchy (if you are on Jira Premium) - it's just that any additional levels of hierarchy need to be above epic. As you can rename your hierarchy levels, you can also model the system that you are looking for; you just have to keep in mind that there are certain semantics 1 accepted. the view like the one in your screenshot is only available for Kanban boards with Backlog, because there you'll have a way to show Epics. But even in this view you can't have the Epic showing "above" the Stories. You can have a more detailed view with the new Roadmap feature, if you configure issue dependencies. BigPicture task hierarchy for epics, stories, and tasks. So I'm using BigPicture plugin along with a project in JIRA Software to manage tasks/projects for marketing team at my job. I was able to arrange the task hierarchy in the WBS so that it was able to automatically nest subtasks under stories. But when I created an epic, I noticed that the How to adjust or change duration of a task under an epic in the timeline. When creating a time line, jira provides editing or changing the time of the Epics. but when a child issue is added to a relevant epic in the timeline, jira does not allow to change the time. it is automatically set to the sprint time line which the issue is included. The Epic issues are linked into the Initiatives with a 'is blocked by' relationship. What we are trying to do is create a query that shows the status of Initiative and the status of the linked Epic so we can verify they are in the correct statuses in accordance with the graphic above. We've tried using ScriptRunner and the standard-issue search In the Epic edit screen, you can click on "Configure" located on the bottom right of the screen. In the right panel (Hidden Fields), you should see "Epic Name". Drag to either the "Description" section or the "Context" section. Click "Save". I added to Context and see it on the right panel of the Epic edit screen. Change the name there and you 1 answer. There is the Epic Report that's a default report, but it won't give you a % Complete based on the number of issues completed within that Epic. Even so, you could easily figure out % Complete using the information on this report. Other than that, you could export the Epic's issues to Excel/CSV from the Issue Navigator and use Excel or Steps: Visit the issues and filters page by click on 'Issues and Filters' in the global view of navigation (if you are in a project, first click on the Jira logo on the top left), then on navigate into 'Search issues': Here you can filter out the issues you want to move using the filter bar. Once your filter is set up, click on the top-right WLlEbR.