Backlog & Sprints

The Backlog page lets you plan work by moving issues between your project's backlog and its sprints, and by creating new sprints - without leaving the app.

The Backlog page

A header with Backlog and a ＋ Create sprint button sits above a row of lanes:

• Backlog (always first) - every issue in no sprint that isn't already Done.

• One lane per open sprint - your active and future sprints; the active one carries a green ACTIVE badge.

Each lane shows its name and a live count. Closed sprints don't appear here - reach those from the board header's sprint menu.

What can (and can't) join a sprint

• Sub-tasks are excluded - a sub-task always follows its parent's sprint.

• Epics are excluded - they span multiple sprints and aren't sprint items.

That leaves standard types (Story, Bug, Task…). The Backlog lane also hides issues that are already Done.

Create a sprint

＋ Create sprint opens a dialog with:

• Sprint name (required).

• Start / End date (optional) - the end can't be before the start.

• Goal (optional).

The sprint is created automatically on the project's first sprint-capable board (a Scrum board, or a sprint-enabled Kanban board); on success it appears as a new lane. If there's no sprint-capable board, creation fails with a clear message.

Move issues

Drag a card between lanes - the target highlights with a dashed outline. All three directions work: Backlog → Sprint, Sprint → Sprint, and Sprint → Backlog. Moves are optimistic: the card jumps immediately and a toast confirms it; if rejected, the card snaps back with the reason. You can also move issues to a sprint from the board's bulk bar and per-card menu.

How sprints are found, and error states

AKB reads every board associated with the project and collects sprints from any that support them - Scrum boards and sprint-enabled Kanban boards. If nothing loads, a "Couldn't load sprints" panel names the cause:

• No agile board is associated with this project.

• The project's board(s) don't support sprints (for example a plain Kanban board).

• A permissions error (HTTP 401 / 403) - a site admin must re-approve the app's Jira Software access under Apps → Manage apps.