Custom Columns
Connected to the same project, people, permissions, and AI context.
Operations
Kanban Tickets for Small Teams
A drag-and-drop kanban board for tickets, with your own statuses, types, priorities and several assignees per ticket.
Unified Organization & Productivity
Difficulty Estimation
Connected to the same project, people, permissions, and AI context.
Several Assignees and Sub-Tickets
Connected to the same project, people, permissions, and AI context.
CSV Import and Export
Connected to the same project, people, permissions, and AI context.
Atty can look up tickets and the board, draft a new ticket or an update, and archive one when you ask. It checks for an existing ticket first, and every change waits for your approval.
Connected to the same project, people, permissions, and AI context.
Working guide
A kanban board app shows each piece of work as a card in a column, so a small team can see what is waiting, in progress and done. The columns should match the stages your team actually checks, and each card needs one clear next step with an owner. This board stays simple on purpose, with no sprints, time tracking or dependency links.
What people search
Kanban board app: 590 average monthly searches.Google Ads Keyword Planner · 2026-10-09 · United States
Workflow map
From an idea to a finished card
| Job | App | What it does here |
|---|---|---|
| Define the columns | Work Board | Create your own statuses, such as To Do, In Progress and Review, and drag each card to the stage it has reached. Keep only the columns your team checks, because a column nobody reads only hides the work. |
| Shape each ticket | Work Board | Choose a type, such as Bug, Story or Task, and a priority from P0 to P5. Size the work with T-shirt sizes or numbers, assign one or more people and add labels so related cards can be grouped. |
| Hold unstarted work | Backlog | Tickets that have not started wait in the Backlog, which sits next to the active board, until someone takes them on. Move a card onto the board only when it has an owner and a clear next step. |
| Bring in an existing list | Work Board | Import a CSV file to move tickets that already exist in a spreadsheet onto the board, and export tickets to CSV when you need a copy. Check the imported rows against the source before the team starts working from them. |
| Archive finished cards | Work Board | Archive tickets that no longer need attention, so the active board stays readable. Archiving takes a card off the board view, so treat it as housekeeping rather than a record of the decision. |
| Ask Atty to draft | Work Board | In chat, Atty can look up tickets, draft a new ticket or an update, and archive one when you ask. Each change waits for your approval before it reaches the board. |
In practice
A week of keeping the board honest
Monday · reset the columns
The team lead reviews the columns with the group and removes a stage nobody uses. The team agrees the new layout before anyone moves a card. Two cards that were marked Done last week go back to Review, because the fix was never tested.
Work BoardTuesday · size new tickets
A repair coordinator writes each new request as a card, picks its type and priority, and sizes it on the team's T-shirt scale. Anything without an owner stays in the Backlog until someone takes it on.
Work BoardWednesday · split a large job
A bigger job becomes several cards, one for each visit or deliverable, and each card gets its own owner and label. The board does not assign the work on its own, so the lead names the person responsible for every card.
Thursday · ask about stuck cards
The lead scans the In Progress column for cards that have not moved in several days and asks each owner what is blocking them. The answer is written on the card, so the next person who opens it sees the reason.
Friday · export and archive
Finished cards that no longer need attention are archived, so the active board stays readable. The lead then exports the open tickets to CSV and uses that file for the weekly summary that goes to the team.
Work Board
Start here
Forms and pages that feed the board
Internal bug report
Decide which steps and expected results a bug needs before a person turns it into a card.
Design request form
Decide what decision a design has to support before its card enters the backlog.
Product roadmap
Decide which outcomes deserve their own columns before you fill the backlog with cards.
Project brief template
Define the finish of a project so it can be split into cards with a clear done state.
Mistakes to avoid
Three ways a board stops telling the truth
Using columns as urgency
A column says where work stands, and P0 to P5 says how urgent it is. Putting urgent work in a column called Urgent mixes the two, so the stage and the priority can no longer be read separately.
Reading T-shirt sizes as a date
A size says how large the team thinks the work is. It is not a deadline, and the board has no velocity chart or time tracking that would turn sizes into a delivery estimate.
Assuming cards depend on each other
Two cards on the board do not block each other automatically, because the app has no dependency links. If one card must finish before another starts, say so on both cards and name the owner of the handoff.
Working checklist
Before a card joins the active board
Make the card actionable
- The title names one result the team can see.
- One person owns the next step, even when several people are assigned.
- The type and the priority match the work.
Keep the board honest
- Every card in an active column has an owner.
- Blocked work is named on the card, with the reason.
- Finished cards are archived rather than left in a column.
What this agreement means
What Work Board includes
- Work Board is a drag-and-drop kanban board for tickets, with statuses you define.
- Each ticket can carry a type, a priority from P0 to P5, a T-shirt or numeric size, labels and several assignees.
- Tickets that have not started sit in the Backlog until they move onto the board.
- CSV import and export move ticket lists in and out, and archived tickets leave the active board.
- There are no sprints, velocity charts, time tracking or dependency links, and Atty drafts tickets for your approval.
Feature evidence: the ticket types, the board settings, the import and export modal and the Backlog app. Use Tasks instead when a simple checklist is enough.
Frequently asked questions
Is a kanban board app the same as a to do list?
Not quite. A to do list shows actions in one list, while a kanban board shows where each card sits across stages. Use the board when stages matter, and a simple list when you only need to know what is next.
Can I name my own columns?
Yes. Create your own statuses, such as To Do, In Progress and Review, and drag cards between them. The columns are a team choice, so keep them to the stages your team actually checks.
Does the board handle sprints or velocity?
No. There are no sprints, velocity charts or time tracking. You can size tickets with T-shirt sizes or numbers, but the board does not add them up into a schedule.
Is Work Board a help desk for customer requests?
No. Work Board tracks team work, not customer cases. For customer problems with a customer record and a resolution, use Customer Care.
Can Atty create tickets for me?
Atty can draft a ticket or an update from chat, and it can archive one when you ask. Each change waits for your approval, so nothing reaches the board unchecked.
More references for this work
Beta Tester Signup
Plan the questions and review process for beta tester signup.
API Access Request
Plan the questions and review process for api access request.
Third-Party Vendor Evaluation
Plan the questions and review process for third-party vendor evaluation.
Architecture Review Request
Plan the questions and review process for architecture review request.
