Creating Epics on the Story Map

Epics from your Jira board line the top of your Story Map. The order of the epics on your Story Map is pulled directly from your Jira board:

To create an epic on the backbone of your User Story Map, place your cursor where you’d like to create a new epic and a plus sign will appear:

Clicking the plus sign will open a ‘Quick Create’ epic box where you can enter your epic name and then tick to save:

You can create multiple epics along the Story Map backbone by hitting enter:


Creating Issues on the Story Map

To create a new issue on the User Story Map, hover over any blank space under an epic and click anywhere in the blue box with the [+] sign.

Clicking on the blue box will create a new issue card. Simply type in the story summary and hit enter to continue creating issues beneath your chosen epic.

You can also create and rank new issues between other issues. Hover between 2 issues and click on the blue [+] sign.

Issues will automatically be linked to the above epic in Jira, and scheduled into the Sprint or Version swimlane that they were created in.

For example, the newly created issue in the video above will inherit the EAUSM-26 - Delicious Space Nutrition epic link, and be scheduled into Sprint 1 on the Jira backlog.


REQUIRED FIELDS
If your project has Required Fields the standard "Create Issue" dialog will appear when you trying to create new issues:


Scheduling Issues without Epics onto the Story Map

Epics from your board line the top of your Story Map and their linked issues sit below them in columns to form the Story Map. This means that only stories linked to an Epic are visible on the Story Map.

All issues that have not been linked to an Epic live in the Issues without Epics panel. The issues without Epic panel can be found in the top right of the Story Map header (shown below):

You can search for existing issues not linked to an epic in this panel by keyword, issue key or quick filters and multi-select and drag and drop them onto the Story Map.

Dragging an existing issue from your Issues without Epics panel onto the Story Map will link the issue to the epic it is placed under, and schedule the issue into the respective Sprint/Version depending on which swimlane it was dropped into.

In the above video, we dragged EAUSM-47 - Issue without epic 1 from the Issues without Epics panel, onto the Story Map. We placed it below epic EAUSM-21 - Book Commercial Space Travel and into the Sprint 1 swimlane. By doing so, we have linked Issue without epic 1 to the Book Commercial Space Travel epic, and scheduled it into Sprint 1 on the Jira backlog.


Editing Epics on the Story Map

Epics can be quickly and easily edited on the Story Map.

Updating the Epic Name

The Epic Name field is what is displayed on the epic cards on the Story Map. To update the an epic’s name, simply click on the epic name, and start typing! Hit enter when you want to save your changes.

Editing other fields on an Epic (Summary, Description, Assignee Components etc.)

Server/DC

You can update additional fields on an epic via the Easy Agile Issue View. This can be opened by clicking on the issue key of the Epic. The Easy Agile Issue View shows native Jira fields that are configured to appear on your Issue Screen.

The Easy Agile Issue View currently shows the following fields:

  • Summary

  • Description

  • Components

  • Assignee

  • Versions

  • Status

  • Sprint

The following field types are also supported, provided they are on the ‘Edit Issue’ screen being used by your Project:

  • Single & multi-line text fields

  • Single & multi-select list fields

  • Numeric fields

In order to view the above field types in the Easy Agile Issue View, your Jira Administrator will need to add any relevant fields to the screen being used by your Project.

Here is a link to an Atlassian doc which walks you through how to add a field to a screen.

We’d love to hear what other field types you would like supported in the issue view here.

The native Jira Issue View can be opened from the Story Map by ctrl+click on Windows or cmd+click on a Mac on the issue key. Alternatively, clicking the issue key in the issue preview editor will also open the Issue in a new tab.

Cloud

You can update additional fields on an epic via the native Jira edit issue modal. This can be opened by clicking on the issue key of the Epic.


Editing Issues on the Story Map

Issues can be quickly and easily edited on the Story Map.

Updating the issue summary

The issue summary is what is displayed on the issue cards on the Story Map. To update the the issue summary, simply click on the issue summary, and start typing! Hit enter when you want to save your changes.

Editing other fields on an Epic (Summary, Description, Assignee Components etc.)

Server/DC

You can update additional fields on an issue via the Easy Agile Issue View. This can be opened by clicking on the issue key. The Easy Agile Issue View shows native Jira fields that are configured to appear on your Issue Screen.

The Easy Agile Issue View currently shows the following fields:

  • Summary

  • Description

  • Components

  • Assignee

  • Versions

  • Status

  • Sprint

The following field types are also supported, provided they are on the ‘Edit Issue’ screen being used by your Project:

  • Single & multi-line text fields

  • Single & multi-select list fields

  • Numeric fields

In order to view the above field types in the Easy Agile Issue View, your Jira Administrator will need to add any relevant fields to the screen being used by your Project.

Here is a link to an Atlassian doc which walks you through how to add a field to a screen.

We’d love to hear what other field types you would like supported in the issue view here.

The native Jira Issue View can be opened from the Story Map by ctrl+click on Windows or cmd+click on a Mac on the issue key. Alternatively, clicking the issue key in the issue preview editor will also open the Issue in a new tab.

Cloud

You can update additional fields on an epic via the native Jira edit issue modal. This can be opened by clicking on the issue key of the Epic.


Updating the Status Category of an issue on the Story Map

In Jira, there are 3 status categories - To Do, In Progress and Done.

The status category of an issue is shown on every card via corresponding status category colour, next to the issue type icon:

Server/DC

Cloud

Viewing the Status of an Issue

In Jira, you can map status' to one of the 3 pre-defined status categories (To Do, In Progress, Done). An issue's status indicates its current place in the project's workflow.

For example:

Status

Status Category

Thinking About

TO DO

In Review

IN PROGRESS

Won’t Do

DONE

To view the status of an issue on the Story Map, simply hover over the status category colour on the card:

Updating the Status of an Issue

You can transition issues and epics between status' without leaving the Story Map. Learn how below:

Server/DC

You can update the status of an issue or epic via the Easy Agile Issue View. This can be opened by clicking on the issue key and using the Status dropdown:

Note: this is not possible for where a transition screen has been defined in the workflow. For more information about creating and editing workflows as a Jira Administrator, see Atlassian’s page Work with issue workflows.

Cloud

You can update the status of an issue or epic via the native Jira edit issue modal. This can be opened by clicking on the issue key and using the Status dropdown:


Estimating Issues on the Story Map

The Story Map uses the same estimation statistic being used by the board it sits. Estimation on the Story Map is compatible with the following Estimation Statistics:

  • Story Points

  • Original Time Estimate

For example, if a board is configured to Story Points, the Story Map will also display Story Points.

Estimates are displayed on the issue cards on the Story Map as below:


To estimate an issue on the Story Map, click on the estimation pill on the issue card, enter your estimation value and hit enter:

You can view a roll-up of estimates by status category on the right-hand side of the Sprint or Version swimlane:

This shows an overview of how many Story Points (or Original Time Estimate) are in the To Do, In Progress and Done status categories for that Sprint or Version.

Estimation is only available on Scrum Boards. While an estimation field can be added to the Issue screen on a Kanban board, this estimation is not included on the User Story Map.

For more information on how Board Administrators can manage estimation statistics, see Atlassian’s page Configure estimation and tracking.


Ranking & Scheduling Issues on the Story Map

Issues can be moved around the Story Map in 2 ways: drag + drop or via the quick actions menu

Drag and Drop to change rank

Issues can be dragged and dropped within their Epic column to change an issue’s rank on the backlog and to visualise priority:


Drag and Drop to change epic link

Issues can be dragged and dropped across epic columns to change the epic link:

In the example above, we moved issue EAUSM-24 from the Pre-flight Zero Gravity Training epic, to the Commercial Space Booking System epic

HOT TIP

You can drag multiple issues from one epic to another, by using the SHIFT key. Press and hold the SHIFT key. With the SHIFT key held, click on the issues you want to move and drag them across to their new epic.


Drag and Drop to schedule an issue into a Sprint/Version

Issues can be dragged and dropped between swimlanes to update the Sprint/Version they are scheduled in:

In the example above, we moved issue EAUSM-5 from Sprint 1 to Sprint 2.

HOT TIP

You can drag multiple issues from one Sprint/Version to another, by using the SHIFT key. Press and hold the SHIFT key. With the SHIFT key held, click on the issues you want to move and drag them across to their new swimlane.

Quick Actions menu to schedule an issue into a Sprint

Issues can also be scheduled into a Sprint using the Quick Actions menu. You can open the Quick Actions menu in 2 ways: right-click or by hovering over the issue and clicking on the menu

Note that drag and drop is only enabled when the Board filter uses ORDER BY Rank. When issues are ordered by a different field like Priority for example, User Story Maps is unable to change the order of issues.


Reordering Epics on the Story Map

Epics can be reordered on the User Story Map using drag and drop.

All of an epic’s linked issues will also move across with the epic. Changing the order of the epics on your Story Map will also change the order of epics on your backlog in the Epics Panel:

Note that drag and drop is only enabled when the Board filter uses ORDER BY Rank. When issues are ordered by a different field like Priority for example, User Story Maps is unable to change the order of issues.


Epic Statistics on the Story Map

In Jira Server and Jira Data Center, a progress bar will show at the top of epic cards on Scrum boards.

This progress bar is pulled in from the Jira backlog and hovering over the blue line on the Story Map reveals the epic statistics.

This progress is calculated based on the Estimation Statistic configured in Board settings (i.e. Story Points or Original Time Estimate).

For example, if the stories linked to an Epic have a total of 12 story points, and an issue worth 3 story points is marked as Done, the progress bar will be at 25%.

Estimation is only available on Scrum boards as it is based on the board’s Estimation statistic. Epic progress is not yet available on Jira Cloud due to a limitation of Atlassian’s API: progress on this feature can be tracked on Atlassian’s Jira Cloud backlog here: JSWCLOUD-14710: Expose Epic Statistics in JIRA Software API.