In such a case the Product Owner had to create a new epic, enter necessary details and move backlog items to it. For such a situation, we added a new command Convert backlog item to epic. Select any backlog item card and choose click the icon in the side view. The backlog item details will be transferred to the new backlog. As a work-around you can: Run a query to get your epic list. Export that result list. Grab just the keys, and convert them into comma-separated values (CSV) using a text editor. Paste the CSV epic list into your second query: "Epic Link" IN (yourCSVlist) AND labels = iPub ORDER BY "Epic Link", Key. Best regards, That is correct - subtasks are useless in Scrum planning and just waste space and make noise. A subtask always belongs to its parent, and that parent can have an Epic, which then implies that the sub-task is inside that Epic. But there's an oversight in that the subtasks don't actually inherit the information internally. Change Epic to Story: What happens to the Stories and tasks that fall under it. New Jira user here. We are currently under a reorg and management has identified some changes. One is that specific Epic should be converted to a story. However, it is a number of Stories and tasks beneath it. If the issue type is changed will the association to the 2 Answers. No, it's not possible the way you want. I suggest the most common approach and that's to use Epic -> Task/Story -> Sub-Task hierarchy. The Sub-Task is the smallest task in Jira and it doesn't make sense to have any further sub-issues. Moreover, (User) Story is bigger piece of delivery than a Sub-Task. Thanks, all. Until the lookup action supports custom fields then, it looks like the answer to my original question is no, there is no way to directly access an epic field's value from a sub-task. My solution is now to copy the needed value from the epic to the parent issue of the sub-task so it can be accessed when needed. Task is a very generalised word, just "someone needs to make some effort to do this". Jira Software's hierarchy is. Epic; Standard Issue Types (Story for example, but Bug, Improvement, and a couple of others are created by default in Jira) Sub-task Issue Types (Technical task and sub-task are the ones you'll see off-the-shelf in Jira) Check Gantt Suite overview video. Configure Gantt chart based on multiple projects, including the team-managed projects. Create what-if scenarios for advanced planning. Plan by sprint. View auto-calculated project completion in percentage. Observe critical path, milestones, deadlines and delayed tasks. Monitor resource workload and availability. Rnyp3.

jira convert task to epic