To promote a feature: On the features page, select Promote f rom the More Actions menu on the toolbar (top-right of the page). Select Feature as an object, and then select a PI and a program. Under Parent, select the feature which you want to promote to a parent epic. Under Child, select the check boxes of the features which will be child 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. The solution I came with: Do a Bulk Change -> Move & select the SubTasks you want to fix. Convert them to Tasks using the bulk move, edit / bulk edit them to delete the epic link, then Bulk Move them back to SubTasks. You'll have to select the parent task when you convert them back to SubTasks so best to do this one set of SubTasks at a time. Epics and Features are higher level containers. User Stories and Tasks are more sub-level components. Epics can DIRECTLY be broken into User Stories/Tasks (aka backlog items) Epics IDEALLY need to be broken down into Features. Features can be broken down into User Stories / Tasks / Backlog Items. These tasks / stories are what fit into SPRINTS. 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 Typically for SW OOB you will see something like: Epic, Story, New Feature, Improvement, Bug, Task or similar. Epic is unique from all other issue types. Stories, New Features, Improvements and Task are all more or less equivalent but obviously have different meanings. They can all have Sub-Tasks and they can all be linked to each other. A specific set of Epics and/or Tasks, or any other Issue Type. The Board Filter controls what is shown on a Board. For example, you could mark all your Epics/Tasks with a specific label, then filter for this label on the board to exclude all "other" Issues; A specific set of Statuses - or a subsection of one Workflow - using the columns settings. 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. oootL2W.

jira convert task to epic