Link the sub-tasks to the Stories. (meaning you now have the parent child & links set up for the sub-tasks) Create the Epic. Link/Epic Link all cloned Stories to the Epic. Now you have the Epic > Story > Sub-task hierarchy. Bulk Move the sub-tasks to tasks (this will drop the parent/child relationship) Select a story (or group of stories) to be moved. Click Move in the Bulk Actions menu. A drop-down menu will appear with a list of available destination projects. Choose a project, then click Apply. To move stories between projects via drag and drop in a Workspace, simply click on a story and drag it to the desired panel within another project. project = PROJ1 AND "Epic Link" = EPIC-123 AND (issuetype = Story OR issuetype = Sub-task) ORDER BY priority DESC, updated DESC But this only returns the stories. I think this is because JIRA reads this as "Retrieve sub-tasks for EPIC-123" (which is 0) as opposed to "Retrieve sub-tasks for stories in EPIC-123". Even if you convert any other type to an Epic in an active sprint, you wont be able to see it in backlog View .. See below . You will see Epic in ACTIVE sprint . See, backlog View: You wont see Epic here . JIRA is design in a way that Epics are only visible in active sprint (Scrum board) not in backlog however its other way around in Kanban Board How To. Step 1. Navigate to Settings, Issues, Issue Types. Add a new Issue Type. The name is user-definable, I’ve named mine SubTask. Select a preset icon or upload one of your own. I use the Jira default Sub-tasks icon. Save. Step 2. Navigate to Settings, Issues, Issue Type Schemes. Make sure you add Labels to issues view screen. You can always add new labels by typing ' L'. Matt Doar. Community Leader. Aug 27, 2019. And also to the edit screen so you can change it. Like. Rene Beck Sep 03, 2019. That did the trick. I must be doing something fundamentally wrong but this simple query does not work in JIRA JQL: issuetype = Epic. In search it works withount any problem, showing me all my epics and if I change to. issuetype != Epic. again it works showing me all non-epic issues. Cat Mumumu Nov 12, 2021. All tasks under Epic seems could not adjust time duration and it is locked for the entire sprint when the task is assigned to a Sprint. Have a look at GIF below only the EPIC WOZI-1 time range could be adjusted, all other sub-tasks under the Epic, the timeframe or duration could not be changed at all. A simpler way is by using an add-on. Hierarchy for Jira lets you create a completely custom issue hierarchy, so you can create levels both above epics and below stories. This makes it easy to create an epic>story>task>sub-task hierarchy and easily link task to stories (or any issues to each other in a parent-child relationship). These would be the exact steps to achieve your need: Create a new select list custom field with the option "Automatically created", adding it to the create screen of your Epics and Tasks. Create a scheduled rule to create the Epic you need and set the Epic with the option "Automatically created" in the custom field you created: Create another eMZvMRF.