10X: Backlog for Epics

A backlog is a prioritized list of work for the development team that is derived from the roadmap and its requirements. The most important items are shown at the top of the backlog so the team knows what to deliver first. The development team pulls work from the backlog as there is capacity for it.

You can manage and prioritize epics and stand-alone features in the epic backlog. Click a title of an epic or a stand-alone feature to open a slide-out panel with more information about that work item. If the epic contains child features or capabilities, you can also click the expand arrow Screen_Shot_2020-02-07_at_10.10.49_AM.png next to the epic name to manage and prioritize the features or capabilities within the epic


  • Estimate. The options for estimating epics are WSJF, T-shirt size, points, and team weeks. You need to set up the estimation method, which is described in the Configure Estimation Settings section.
  • Pull rank. You can use a theme rank to sort epics and stand-alone features. This option is available only if you have a program and a PI selected on the Configuration bar. Otherwise, to prioritize your epics and stand-alone features, you can drag them to the necessary position. The ranking is disabled if filtering is on. As epics can span multiple program increments, epic rankings are independent of the program increment.
  • Story points. A total sum of story points belonging to the epic or stand-alone feature.
  • Rank. This is the rank of a work item in the PI selected. If no PI is selected, this is the overall rank of the work item for the program or portfolio selected.
  • State. A state of an epic’s development.
  • ID. A unique ID for an epic or a stand-alone feature.
  • Name. A name of an epic or a stand-alone feature.
  • Toggle views:
    • Program. The program the epic or stand-alone feature belongs to.
    • Schedule. The sprint the epic or stand-alone feature will be delivered in.
    • Parent. The parent theme of the epic or stand-alone feature.
    • Tags. Tags that are used to make it easier to find an epic or a stand-alone feature.

Columns shown

The Columns Shown option offers to select which columns to display, providing some level of customization.

For the Epic Backlog, you can choose to view such columns as Strategic Driver, Dependency, Acceptance Criteria, Age, Blocked, Budget, Capitalized, Chat, Child Count, Customers, Investment type, MVP, Owner, Points (an estimate set for an epic), Process Step, Score, Story Point Progress, Story Points (sum of LOE on stories associated with an epic), Tag, T-Shirt size, Type, Value, Weeks, and WSJF. 

Additionally, you can select custom fields that you have created for epics in Details Panels Settings. Only fields that are set as Active in Details Panels Settings are available for selection as columns in the backlog.

You can find out more about these columns in the Manage Epics topic.

  • Score shows the epic score from the Value tab on the epic details page so that you can rank your epics in the backlog according to the value score.


With the available filtering options, you can filter epics and stand-alone features by state, process step, theme, type, value, capitalized, blocked, title, T-Shirt, tag(s), investment type, strategic driver, owner, and MVP.

Quick add

In the backlog, you can quickly add a new epic just above the list of all epics.

To add an epic:

  1. In the New Epic Name box, type the title for the epic.
  2. Click Add. The epic is automatically prioritized at the bottom of the list and is assigned to a program, team, program increment, or sprint based on where it was added from.

Moreover, you can add child features to an epic. Go to an epic you want to add a feature to, type the feature's name, and then click Add.

Note: If you work with stand-alone features instead of epics, you can add a story to that stand-alone feature.

Right-click menu options

For faster navigation in the backlog, right-click an epic to do the following:

  • Open in new tab. Open the work item in the full-page view in a new tab.
  • Duplicate. Copy the existing work item. You need to type a new name for the duplicate work item. The name must be unique. The work item is added to the bottom of the list and assigned to the same team and program increment/sprint that the original work item is assigned to.
  • Move To Top. Move the work item to the top of the list the work item is contained in.
  • Move To Bottom. Move the work item to the bottom of the list the work item is contained in.
  • Move To Position. Select the place to move the work item to. It is useful when you have a long list and dragging the work item is not convenient.
  • Move To Program Increment. Move the work item to a certain program increment or an unassigned backlog.
  • Move To Recycle Bin. Move the work item to the recycle bin if you no longer need it.
  • Move To Parking Lot. Move the work item to the parking lot to reserve it for later.

Parking lot
Parking lot is used to reserve epics and stand-alone features that have some issues or unanswered questions to come back to them later. You can find the parking lot at the bottom of the epic list. 

See also

Backlog for Themes

Backlog for Capabilities

Backlog for Features

Backlog for Stories

Was this article helpful?
0 out of 0 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.