10X: Manage Stories with the Story Grid

The story grid represents all stories for all teams and sprints to which you are assigned. To open the story grid, go to Team > Stories.

The story grid provides a number of options for stories to manage them effectively.

Grid columns

  • ID. Unique ID for the story.
  • External ID. External ID of a story. It is used if you integrate Jira Align with the third-party tools.
  • Story. Story name as entered.
  • State. Current state of the story. There are the following story states:
    • Pending. A story is pending approval.
    • Ready. A story is ready to start.
    • Building. A story is in progress.
    • Testing. A story is completed by developers (dev complete).
    • Tested. A story is tested (test complete).
    • Accepted. A story is accepted.
  • LOV. Level of value of the story.
  • LOE. Level of effort of the story.
  • Sprint. Short name of the sprint in which the story is scheduled.
  • Blk. Indicates whether the story is blocked.
  • MMF. Indicates whether the story is a minimal marketable feature.
  • AC. Count of acceptance criteria.
  • Chat. Discussion thread for the story.
  • Spec. Count of specifications of the story.
  • UI. Count of user interface designs of the story.
  • Tasks. Total number of tasks to complete the story.
  • Hours. Total number of hours of all team members estimated to complete the story.
  • Trace. All information about the story, such as story name, its sprint, releases, projects, programs, teams, defects, and other information.
  • Select. Select a checkbox and an option from the Actions menu to update the story.

Note:

  • You can click headers to sort the list by the story ID, Story, State, LOV, LOE, and Sprint.
  • Only fields that are set as Active in Details Panels Settings are available for selection as columns on the grid. 

Filter by program increment

When you filter the story grid by a program increment, stories will display on the page depending primarily on their sprint assignment. Stories will display if they are assigned to sprints that belong to the filtered program increment.

This is useful to know in rare cases where a story is assigned to a sprint that belongs to one PI, while directly assigned to a different PI. This same logic is used on the Work Tree (Bottoms-Up view), Program Increment Progress, and Program Room pages.

Example
Program increment A is the parent of sprints 1, 2, and 3. Program increment B is the parent of sprints 3, 4, and 5. A story is created, and in its Details panel, the Sprint field is set to Sprint 1 while the Program Increment field is set to Program Increment B.

After setting the Configuration bar or page filters to Program Increment B, the story will not display. The grid must be filtered by Program Increment A to display the story, as the sprint’s association to its parent program increment is used to filter stories.

Exception: If the story is not assigned to any sprints in the example above, but the Program Increment field is set to Program Increment B, then filtering the grid by Program Increment B will display the story.

 

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.