Mass edit stories

For a more efficient work process, you can edit several stories at once, assigning them to the same features, teams, and sprints.

Note that mass edit functionality uses the same validation as editing of a single story. If any change to a story contradicts the existing rules, that story won't be updated.

Important: Mass editing is available only when one program is selected using the page filters or sidebar, and at least two stories are selected.

To mass edit stories:

  1. Select Items in the top navigation bar.
  2. Select Stories; the stories page displays.
  3. Select Apply Filters on the toolbar (top-right of the page).
  4. Filter by a single program, and then select Filter.
  5. Select the stories you want to edit by selecting the corresponding check boxes on the right of the grid. Select the check box next to Sel to select all stories. You need to select at least two stories for the mass edit option to be available.
  6. From the More Actions menu, select Mass Edit.
  7. Select the feature you want to assign the selected stories to. The list includes all features associated with the program filter or sidebar selection. Accepted features aren’t shown here.
  8. Select the team you want to assign the selected stories to. The list includes all Agile teams mapped to the program filter or sidebar selection. Only active teams are shown.
  9. Select the sprint you want to assign the selected stories to. The list includes sprints based on the program filter or sidebar selection and on the team selection in the previous step. Only sprints that are in the Not Started or Planning Phase states and Unassigned Backlog are available for selection.
  10. Select the release vehicles you want to assign the selected stories to. The list includes all release vehicles. Release vehicles will not be shown if disabled in Details Panels Settings. 
  11. Select the owner you want to assign the selected stories to. The list of owners is based on the program filter or sidebar selection.
  12. Click UpdateWhen you perform a mass edit on one or more work items, all items must comply with existing editing rules for the type of item, and the role permissions of the user attempting the edit. If one or more items violate a rule, they will not be updated as part of the mass edit. Eligible items will be updated.
  13. A message displays at the top of the screen, indicating how many items were updated out of the total attempted:

Note: Access to Mass Edit is controlled by the Manage Agile Objects(Admin) system role toggle.

Validation rules

Rules for updating stories using mass edit are summarized below, by field:

All fields

  • Stories assigned to completed sprints will not update. Exception: Mass edit performed by user with the Super Admin system role.

Feature

  • The chosen feature in the drop-down must belong to the same PI as the story selected for edit.

Team

  • The Team field will not update on stories assigned to locked or completed (done) sprints. Exception: Mass edit performed by user with Team Coach role that has both Mass Edit and Manage Agile Objects (Admin) permissions enabled.
  • The Team field will not update on stories assigned to planning or not started sprints. Exception: Mass edit performed by user with Scrum Master, PO, or Team Coach role that has both Mass Edit and Manage Agile Objects (Admin) permissions enabled.

Sprint

  • The Sprint field will not update on stories assigned to locked or completed (done) sprints. Exception: Mass edit performed by user with Team Coach role that has both Mass Edit and Manage Agile Objects(Admin) permissions enabled, or by Super Admins.
  • The Sprint field will not update on stories assigned to planning or not started sprints. Exception: Mass edit performed by user with Scrum Master, PO, or Team Coach role that has both Mass Edit and Manage Agile Objects (Admin) permissions enabled.
  • You can't assign stories to a completed sprint using mass edit.

Release Vehicle

  • The drop-down for this field will be disabled if the selected program does not have release vehicles enabled for stories.
  • Users must have the Scrum Master, Product Owner, or Team Coach role to mass edit release vehicle. 

 

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.