Hi all, Our Jira issues are structured like this: Epic -- User Story -- Tasks. There's (typically) 1 Epic per release. We use 1 User Story per 1 webpage that we're updating, then we do 1 Task per each stakeholder (ex: developer, QA, UAT; story points are recorded here). Via the Backlog. From your project’s sidebar, select Backlog. On the Backlog, select the Epic filter and enable the Epic panel toggle. Select the Epics you want to view/edit. Their details will appear to the right of the Epic panel. Click an Epic's chevron ( >) in the panel to view and edit more details. The way it appears achievable is that as an Epic is created, you can add issues to it in the form of stories. However after defining a story as if it were a new (sub-) project, you can then select the stories icon and change it to an Epic of its own. The new Epic stays subordinate to parent Epic but can now contain stories of its own. Edit multiple issues. This bulk operation allows you to edit multiple issues at the same time. The available bulk edit operations depend on the issues selected and the nature of the fields you want to change. Select Edit Issues and select Next. Choose what information to edit. 1 level: Initiative -> linked to Jira issue type INITIATIVE. 2 level: Epic -> linked to Jira issue type EPIC. 3 level: Stoy -> linked to Jira issue type STORY. 4 level: Sub-task -> linked to Jira issue type SUB-TASK . When setting up a plan for that specific project with roadmap view, I am not able to see the breakdown by Initiatives. How is
Go to the Backlog for your project. On the top of the backlog page, select the desired epic. At this point the backlog section only shows the issues belonging to the epic and clicking on "add new issue" at the bottom of the section automatically adds the new created issues to the epic. Another way to achieve the same result would be to create
Click the issue and click 'Task' in the top left in an attempt to convert the Task to a Subtask. It only allows issue to be changed to Epic or Story even though Subtask is clearly a defined issue type for our project. Click the issue and click Move. Here the UI gives the impression that you can actually change the Task to a Subtask and choose a
1K3wuN.
  • 0xx8q7ob55.pages.dev/678
  • 0xx8q7ob55.pages.dev/941
  • 0xx8q7ob55.pages.dev/615
  • 0xx8q7ob55.pages.dev/712
  • 0xx8q7ob55.pages.dev/380
  • 0xx8q7ob55.pages.dev/664
  • 0xx8q7ob55.pages.dev/397
  • 0xx8q7ob55.pages.dev/276
  • 0xx8q7ob55.pages.dev/338
  • 0xx8q7ob55.pages.dev/403
  • 0xx8q7ob55.pages.dev/384
  • 0xx8q7ob55.pages.dev/304
  • 0xx8q7ob55.pages.dev/371
  • 0xx8q7ob55.pages.dev/865
  • 0xx8q7ob55.pages.dev/334

    • jira change task to epic