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. Solution: Add epic to the sprint. How: A. If your project setup lets you see the epic ticket in the backlog view still, just drag the ticket to the sprint section on top. B. If your project doesn't let you see the epics in the the backlog view anymore, you have to enable to "Sprint" field in the epic view screen. Answer accepted. To update this Question, today as of March 4th, 2019, you CAN convert a Task or any type of issue into a sub-task, just by clicking the 3 dots () icon to the far right of the issue title and selecting MOVE. In the Move issue screen, you must select the sub-task (you got to have it enabled or added as an issue type in the 1 accepted. In a project roadmap you can only see issues from that project. If you're on the Premium plan then you get access to Advanced Roadmaps - a different product (formerly Portfolio but now integrated into Jira Premium) which will allow you to arrange multiple projects/boards/filters in one view. It's pretty good, but at an added cost. Once this is done, click on the 3 dots located in the right corner and click on "Bullk change". This next screen will appear, check all issues and click next. On the next screen, select the "Edit issue" option and click Next. Now on this next screen, search and select the "Epic link" field. . A "workaround": create a dummy Story. move the Epic with its child issues. select for the Epic the new type "Story" and for the child issues select "Sub-Task", which forces you to select a Story. choose the dummy Story. execute the move operation. your Epic is a Story and its child Tasks are Sub-Tasks of the dummy. Just paste your Jira link on a Confluence page and it will automatically drop a dynamic Jira issue link on your Confluence page. Once you publish the page, the link will display the issue ID and title, issue category (epic, task, etc.), and issue status in the workflow (to do, in progress, done, etc.). I have defined a Jira Project with a number of Initiatives. Under each Initiative, there is a number of Epics that originate from different Jira Projects. Under each Epic, there are tasks that come from different Jira Projects. I am struggling to find a query that will dynamically list all of the Epics and Tasks that are added to the Initiatives. Under Jira GreenHopper (v6.0.6) there is a new feature. Jira > Agile > board > Plan, drag and drop the Story Issue onto the Epic. Using an old view, navigate to the story page. There should be a Epic Link field. Clicking on it and changing the value of it, should move story to the appropriate Epic. This makes it easy to keep track of the progress and status of your epic. Jira Epic vs. Task. Jira tasks are used to plan specific tasks that would take ~1 day for the team to complete. As each task is completed, the team will edge closer to completing the overarching theme of the project; the Jira epic. Features of a Jira Task:

jira convert task to epic