Backlog and Active Lists
See tickets not started yet in one list and active tickets in another, or switch to a table of every ticket.
A built-in feature of Work Board.
The Backlog is the Work Board's list of tickets not started yet, shown next to the active ones. Tickets wait here until you move them onto the board.
See tickets not started yet in one list and active tickets in another, or switch to a table of every ticket.
Filter by assignee, including only yours or unassigned, by status and by labels, and show archived tickets when you need them.
Paste text, upload a file or record a voice note, and Atty drafts a ticket you review in the editor before saving, or adds the details to an existing ticket you pick.
Bring tickets in from a CSV file or export them to one.
A backlog management tool holds work your team has suggested or agreed to consider but has not started, so the active board stays focused on work in progress. Each item needs a clear title, an owner or an explicit unassigned state, and a priority that tells the team what to look at first. Move an item onto the board only when someone has agreed to start it.
Backlog management tool: 140 average monthly searches.Google Ads Keyword Planner · 2026-10-09 · United States
| Job | App | What it does here |
|---|---|---|
| Hold the idea without starting it | Backlog | Add the ticket from the Backlog list, which shows tickets not started yet next to the active ones. Give it a type, a priority from P0 to P5 and any labels the team already uses. It stays out of the active columns until its status moves to a to-do or in-progress status. |
| Draft the ticket from a message | Smart Tickets | Use the Atty option in the add menu and paste a supplier email, add a screenshot or record a voice memo. Atty proposes a title and a description with acceptance criteria, and the ticket opens in the editor so you can correct it before it is saved. |
| Ask Atty what is waiting | Atty Chat | Ask in chat which backlog tickets have no owner or who holds a given ticket. Atty can read the backlog and draft a new ticket, but before it creates one it looks for a similar open ticket and asks you whether to update that one instead. |
| Move a chosen ticket onto the board | Work Board | When work starts, change the ticket to a status that belongs to the to-do or in-progress category. Statuses are set for each project, and the Work Board shows active tickets in columns by status. Once the status changes, the ticket moves from the backlog list into the active view. |
Open the Backlog, switch to the table view and filter for unassigned tickets. Read each title and set a priority only where the request has a real deadline or cost. Tickets that cannot start this month can stay in the backlog without a date.
BacklogTwo people often ask for the same change in different words. Search the backlog for the key term, keep the ticket that already has the context, and add the second request to its description. Archive the duplicate once nothing in it is unique.
In the planning meeting, filter by one label at a time, such as website or billing, so each group reviews its own area. Export either all tickets or only the currently filtered set to CSV if the group wants a spreadsheet, then record the decisions back in the tickets.
BacklogWhen someone agrees to take a ticket, assign that person, move the status to a to-do or in-progress status and add a comment that says what finished looks like. The comment gives the owner a shared definition to check against before closing the work.
Work BoardArchive tickets that the team has decided not to do, so their description and history stay on record. When an old request comes back, turn on the archived view to find it. Restoring the ticket is a change to its archived state, not a new ticket.
BacklogCollect the problem and the workaround before a request reaches the backlog, so triage starts from a job rather than a proposed solution.
Separate feedback about a recent task from general opinions, so only the gaps people actually hit become backlog tickets.
Decide which backlog items belong on a roadmap, and show how certain each one is before the team promises a date.
Close the loop on finished tickets by writing what changed in plain words for the people who will notice it.
A backlog with no review turns into a list nobody reads. Set aside time to triage it and confirm each priority when you do. Archive what will not happen. A ticket that sits untouched for months should be re-confirmed or archived, not left as an unspoken promise.
A P0 to P5 priority is a label that a person sets. Setting P0 does not start the ticket or move it onto the board. Agree in the planning meeting which items get worked on next, and let the status change show when work has actually begun.
The Backlog has no sprints and no story-point velocity. A team that needs sprint planning should keep that method somewhere else. Use the Backlog for intake, grouping and priority, and use the Work Board for statuses while work is in progress.
Based on the Backlog page and its filters, the ticket type and priority fields, the CSV import and export, and Atty's backlog and ticket tools. The Backlog has no sprints or story-point velocity.
It keeps work that has been suggested or agreed but not started, so the active board stays focused. A good one lets you see unstarted items by owner, label and priority and move an item onto the board when work begins.
Not quite. A product backlog in agile planning often feeds sprints and story-point estimates. The Backlog in Attain OS is an intake list for tickets, with types and priorities. It has no sprints or velocity reports, so a team that needs those should plan them with a separate method.
A kanban board shows work moving through status columns. A backlog holds work that has not entered those columns yet. Many teams use both: the board for work in progress and the backlog for what is waiting.
No. The backlog holds internal work items that your team plans and does. It is not a help desk inbox for customer messages. Customer requests that need a case record belong in the Customer Care app.
Yes, if it is in CSV form. Download the template from the import screen so the columns match, import the file, and then check each imported ticket's type, priority and status. Review the priorities after an import, because the file only carries what someone typed into it.
Plan the questions and review process for external bug report.
Plan the questions and review process for design/ui request.
Plan the questions and review process for architecture review request.
Prepare the content and structure for release notes.
Prepare the content and structure for onboarding guide.
Prepare the content and structure for status page.
Prepare the content and structure for code snippet library.