Backlog & Approval

Every board in Spedy has a Backlog -- a dedicated space for tickets that are not yet ready for active work. The backlog helps you collect ideas, plan upcoming work, and optionally require approval before tickets move into your workflow.

Accessing the backlog

Click on the Backlog tab in your board navigation (next to the Kanban view). The backlog shows all tickets in the Backlog status, which belongs to the Planning category.

How the backlog works

Tickets in the backlog are not shown on the main Kanban board by default. They live in a separate view where you can:

• Review and refine ticket descriptions
• Set priorities and assign team members
• Add labels and estimates
• Decide which tickets are ready to move forward

Approval workflow

Boards can optionally require approval before a ticket leaves the backlog. When this is enabled:

1. New tickets are created in the Backlog status
2. A team member with the right permissions reviews the ticket
3. They click Approve to mark it as ready
4. The ticket can now be moved to Todo or any other active status

This is useful for teams that want a gate between "idea captured" and "work started" -- for example, to ensure tickets have clear descriptions, acceptance criteria, and estimates before development begins.

Moving tickets out of the backlog

Once a ticket is approved (or if approval is not required), you can drag it to the Kanban board or change its status to any active column like Todo or In Progress.

Moving tickets back to the backlog

Tickets can be moved back to the Backlog status at any time -- for example, when requirements have changed or a ticket wasn't ready after all. The status transition logic explicitly allows the return path from any status to Backlog.

Grouping the backlog by Epic

The backlog can be grouped by Epic so you see which stories already belong to a larger initiative and which are still standalone.

• Use the Group by dropdown at the top of the backlog and pick Epic. Tickets are then listed under their parent Epic, with standalone tickets shown in a separate No epic group.
• Your choice is remembered per board -- come back to the backlog later and the same grouping is applied.
• Pick None in the same dropdown to return to the flat list.

To attach a backlog ticket to an Epic, open it and set the Epic field (see Tickets for details).

Bulk actions in the backlog

When you have a lot of tickets in the backlog, you can act on many at once instead of clicking through them one by one.

• Select tickets with the checkbox on each row. A Select all checkbox in the header toggles the whole visible list.
• Once at least one ticket is selected, the bulk action toolbar appears at the bottom of the screen and lets you:
  • Change status -- move the selected tickets to any status in one step
  • Change assignee -- reassign all selected tickets to the same person, or unassign them
  • Change type -- assign the same ticket type (Bug, Feature, etc.) to all selected tickets
  • Assign / remove epic -- attach the selected tickets to an epic or remove the association
  • Delete -- soft-delete the selected tickets after confirmation
• Up to 500 tickets can be changed per bulk action. If you select more than 50 at once, Spedy shows a confirmation dialog before applying the update so you can catch accidental large selections.
• Bulk delete is a soft delete -- tickets are hidden but can be restored by an admin if needed.

Tips

• Use the backlog as a staging area for upcoming sprints or iterations
• Combine with labels to categorize backlog items by theme or priority
• Use the AI assistant to generate ticket details before moving items out of the backlog