Skip to content

Sprint

The Sprint column shows the issue’s active sprint along with a state badge — Active, Future, or Closed. You can move an issue into a different sprint, or out of sprints altogether, right from the cell.

  1. Click the Sprint cell of the issue.
  2. A dropdown opens listing the open sprints (Active and Future) for the project’s Scrum board. Closed sprints aren’t shown since Jira doesn’t allow moving active issues back into them.
  3. Pick the target sprint, or choose None to remove the issue from all sprints.

The cell updates in place with the new sprint name and state badge.

Foundation only offers sprints that are currently open on the issue’s project board:

  • Closed sprints — hidden. Jira rejects writes that put issues into closed sprints.
  • Sprints on a different board — not shown. An issue can only belong to sprints on its own Scrum board.
  • Kanban projects — no sprints exist. The Sprint column shows and isn’t editable.

If you expect a sprint to appear and it doesn’t, confirm it’s open on the same board as the issue.

  1. Shift-click or check-box select the rows you want to move.
  2. Use Bulk edit from the toolbar.
  3. Jira’s native bulk move handles multi-sprint writes correctly and gracefully.

Selecting many issues and editing their Sprint cells one at a time also works, but bulk edit is noticeably faster for more than a handful of rows.

The state badge next to the sprint name tells you what phase the sprint is in:

  • Active — sprint is running.
  • Future — planned but not started.
  • Closed — already wrapped up.

Foundation caches the list of sprints for a few minutes to keep the dropdown snappy. A brand-new sprint created in Jira may take up to 5 minutes to appear in the picker.