Boards

Plan and track work as cards in columns: your own, shared with your organization, or kept in step with API Tester projects and Jobs & hiring roles. Insights shows how a board is going.

• Create a board and add cards - Create a board where you are working, add cards to its columns and move them.
• Switch between board, list, calendar and timeline - See the same cards as columns, a table, a calendar or a timeline, reschedule by dragging, and know what others see change.
• Plan dates on the timeline - See cards as bars between their start and due days, grouped under their parent, and move them by dragging.
• Find and filter cards - Search a board, narrow it with filters, save a view, find your own work and share a card.
• Edit a card - What a card holds, how to assign it and get notified, and where its history is.
• Ask for approval on a card - Ask one or more board members to approve a card, answer on the card, and let a column take only approved cards.
• Estimate cards and run an estimation session - Give a card an estimate, or let the team vote on cards privately, agree and save the result to them.
• Add your own fields to cards - Track what your team needs on every card, such as a customer, a severity or a link to the spec, then filter, sort and automate with it.
• Add a checklist, comments and files - Break a card into steps, discuss it, mention a teammate and attach files.
• Break a card into child cards - Link cards under a parent, split its weight between them and see progress roll up.
• Read progress, pace and health - What the three numbers on a card mean, where each comes from and how to change the board's thresholds.
• Share a board and choose who can open it - Make a board private, open it to its team, the teams below or everyone, or share it with a person, a team or a role.
• Link cards, web pages and checks - Attach web links, relate cards to each other, and let a card turn red or green with the tests it follows.
• Give a card to a coding agent - Let your own coding agent build one card: it gets the card's package and a credential for that card only, and its pull request is judged by tests it cannot change.
• Start a product board - Follow every feature from an idea to the live site on one board, with seven stages: Idea, Design, Plan, Develop, Test, Release and Live.
• Read a Feature card - See where a feature stands, what happens next and why, and what it has cost, on one card.
• Add an idea and use suggested ideas - Write one sentence for a new feature, or take an idea {{brand}} found in the records connected to the board.
• Have AI draft a feature's design and approve it - AI draws the screens, APIs and tables from the card's sentence. A person checks the draft and approves it with their password.
• Plan a feature: tasks, builders and checks - {{brand}} drafts the tasks and checks from the approved design. You choose who builds each task, then approve the plan.
• Develop a feature: branch, agents and instructions - Push code to a branch named with the card key, give tasks to a coding agent, and leave notes for whoever builds.
• Test a feature and move it to Release - Checks run on the pull request. When they pass and the code is reviewed and merged, the card moves to Release.
• Release features and watch them live - Plan a release, ship it, let the release check confirm it on the real site, and see which live features work or are broken.
• Compare product boards in the Portfolio - See every product board you can open side by side: features by stage, red and broken ones, releases and progress.
• See where the time went - See how long each feature took from idea to live, where it waited, and how the team and each release did.
• Set goals and see if they are on track - A goal groups epics. Its progress comes from their features, and it tells you early when it falls behind.
• Choose how features move: steps, presets and locks - Set which steps AI does, which {{brand}} does and which a person decides, for a board or for one card.
• See what AI cost for a card or a board - Read the AI calls made for one feature or a whole board, by kind of work, with an estimated cost.
• Triage, fix and verify a bug - Confirm a reported bug, mark it fixed and record the retest.
• Turn a bug's failing run into a regression check - Make the failure behind a bug a check of its own; when it passes again the card closes itself, and the check stays to guard against the bug coming back.
• Set up columns and workflows - Add, rename and reorder columns, group cards a second way, and know what deleting one does.
• Find your way around board settings - The four groups of a board's settings and the row you want in each.
• Add and change card types - Rename the kinds of card, add your own, choose the default and understand behavior.
• Move, archive and restore a board - Move a board between workspaces, file it under a team, and put cards or boards aside and bring them back.
• Import cards from a file - Bring cards in from a spreadsheet, a Trello board, or a Jira, GitHub or Asana export, check a preview first, and undo the whole import in one step.
• Keep a board in step with Jira, Azure Boards, Trello, Linear or GitHub Issues - Connect a board to one Jira project, Azure Boards area, Trello board, Linear team or GitHub repository, map the fields, and changes move both ways - nothing is ever deleted on either side.
• Work faster with keys and quick create - Move through cards with single keys and make a card from one typed line.
• Connect an API Tester project to a board - Send a project's bugs and stories to a board, and create a bug or story from a request or run.
• Automate a board with rules - Make the board move, assign or update a card, or tell people, when something happens to it or when time passes.
• Order rules and see what they did - Know how rules run in order and chain, read a rule's recent runs and fix one that cannot run.
• Let cards move when the work happens - One switch: a merged pull request sends its card to testing, passing tests move it to done with the evidence, and a check failing later brings it back.
• Read a board's pulse - See how many cards a board finishes each week and how long they take once work starts.
• Spot stuck and at-risk cards - See how old the work in progress is compared with finished cards, and which cards need attention now.
• Forecast when work will be done - See a likely finish day, with a range, for a parent card, for the cards a view shows or for a cycle, from your team's recent pace.
• This week on a board - See what moved, what was finished, what became blocked and what is at risk on a board over the last seven days, and have AI write it up for the team.
• Read how a board is going: Insights - One sheet with this week, the forecast, the report, the pulse and the flow of a board.
• Card keys - Every card has a short key such as PAY-12. Say it in a meeting, type it into search, or write it in a comment or a commit to point at the card.
• Send board news out and connect GitHub or GitLab - Post card news to Slack, Teams or your own service, and link branches, commits and pull requests to the cards they name.
• Card templates and cards that come back - Save the cards you make again and again as templates, and let the board add routine cards by itself every day, week or month.
• Flow: where work piles up - A cumulative flow diagram shows how many cards sat in each column day by day, with one line that says what the picture means.
• Invite a guest to one board - Let a customer, a contractor or a partner follow one board with you. A guest sees that board and nothing else of your organization.
• Share progress with your client - Invite your client to one simple page: what is under way, what is done and what waits on them. You decide what they see.
• Send email to a board - A board can have its own email address. Forward a mail to it and it becomes a card, with its attachments.
• Collect requests with a form - Give a board a form: every answer becomes a card in the column you choose. Share it with your workspace or with anyone by a link.
• Spot duplicate cards and draft acceptance criteria - See cards that already say the same thing while you type a title, and let AI draft acceptance criteria that you choose from.
• Read and download the board report - Read a board's totals, download them as Word or Excel, and run Boards reports in Analytics.
• Find a board's bottleneck with its flow reports - Four Boards reports: time in each column, created vs resolved, scope change in a cycle, and the cycle time scatter.
• Get a card ready for a coding agent - Read the card's readiness, fill what it asks for in place, and give the card when nothing blocks it.
• Write a bug a coding agent can fix - Give a bug its facts in place: where and how often it shows, the steps, a lead on the cause and worked examples.
• Say when a card is done - Write the card's done-when lines, link each to a test or a person, and say what is out of scope.
• Refactor and spike cards - Say what a card asks - build, fix, refactor or find an answer - and give a refactor or a spike its own facts.
• Card templates per kind - Save a template whose cards start with their brief: done-when lines, scope, evidence and intent.
• Leave notes for whoever builds a card - Add a builder note on any card, or keep a comment for the builder, so a person or an agent reads it.
• Say what a file shows - Give a screenshot or a log a one-line caption that a coding agent reads with the file.
• Tell agents how to build and test - Set each repository's build, test and start commands and the test environment's rules for every agent on a board.
• Write a board's ground rules - Write short lines every card's package carries: who it is for, principles, non-goals and lines never to break.
• Choose what the agent reads - Leave layers out of a card's package, each with a reason, and copy the package as Markdown.
• Answer an agent's question - Answer what a coding agent asks on its card, and approve its plan when the card was given plan first.
• Give several cards to agents - Start one run of coding agents for picked cards, a main card, a goal or a whole board.
• Resume a run or send a step back - Resume a paused run, send one card back to its agent, or mark it done by a person.
• Hear when a run pauses or finishes - Send a webhook when an agent step opens or is done, and when a run pauses or finishes.
• Review a hand-off note - Read what one card's agent left for the next card, and keep it as reviewed.
• Related work and overlap - See the open cards related to one card, who holds them, and where the work overlaps.
• The session plan - See which cards share one agent session, what that saves, and change it in place.
• Let a bug report ask the right questions - A client's "Something is wrong" and "Create bug" fill in a bug's steps, what was expected and what happened, so nobody types them twice.
• Settle careful-area questions before an agent starts - A card that touches payments, sign-in, personal data or the database asks a few questions first; AI can draft them on a click.
• Ask the agent for its plan first - Give a card "Plan first" so the agent shows its plan and waits for your approval before its pull request is judged.
• Use one-time codes in API tests - Test a sign-in with two-step codes: keep the authenticator's secret as a variable and let each request make the current code.
• Make sure the preview runs the newest commit - Tell API Tester where your preview says its commit, so an agent's round runs only on the code it is about, and let the agent check its preview first.
• Run a card's coding agent in your CI - Let your own coding agent build one card inside GitHub Actions or Azure Pipelines, with your AI key and the card's credential.
• Start each card of a run with kamocore runner - Run kamocore runner on the machine with your coding agent, and each card of your run starts there as soon as it opens.