TanaOutliner
Log inDownload
Guide

Build a shared issue tracker with a type

Create an Issue type so your team tracks work the same way: shared fields, one board, and the AI filing new issues in, complete and consistent, from a meeting or a chat.

Every product and tech team tracks issues: bugs to fix, changes to make, things that need doing, each with a priority, an owner, and a state. In Tana you turn that into one shared tracker by giving issues a type.

Create an Issue type once, and every issue shares the same fields and shows up on one board, whether a teammate files it by hand or the AI files it from a standup. This guide sets that up: the type, the board, and letting the AI keep it fed.

Create the Issue type

1
Create the type in your team's space

Ask the AI to "create an Issue type," or add one from the create menu, in the space your team works in so everyone shares it. A type is for a kind of thing you have many of, and an Issue is the textbook case.

2
Give it the fields that matter

Add the fields an issue always needs: status, priority, the area it affects, and an assignee. Every Issue from now on carries these, so nothing arrives half-described.

3
Add a workflow so issues move on a board

Give the type a workflow, a set of states like Triage, In progress, and Done. With a workflow, the type's page becomes a kanban board: move an issue from Triage to Done and everyone sees it move.

Let the AI file issues in, complete

The point of the type is that new issues land already in shape. When one comes up in a meeting or a chat, the AI creates an Issue with the fields filled, status, the area, who raised it, as a proposal you review and accept. Nothing lands until you say so.

To make this dependable, set the type's AI instructions: "capture what needs to happen and why, set priority from how it is described, and for a bug include steps to reproduce." Now every issue the AI files matches how your team writes them, and you stop chasing people for the missing details.

See every issue in one place

Open the Issue type page and you have every issue across the team, as a list or as the board. Filter to all the open ones, or just the ones for one area, with nobody assembling a report. Because the type lives in your team's space, it is the same board for everyone: the shared source of truth for what is open and who has it.

Add a one-click action

Attach a skill to the Issue type and it becomes a one-click action on every issue: "file this in GitHub," "post it to the team's channel." The skill does the same job the same way every time, so sending an issue upstream is one click for anyone on the team, not a copy-paste ritual. (Filing to GitHub or Linear needs the integration connected.)

Where to go next

Create AI agents with skills and integrationsCreate your own AI agents in Tana just by describing them: assistants you equip with skills and integrations that work on demand, in meetings, or on a schedule.
How to work with your team in TanaThe recommended way for a product or tech team to work in Tana together: how meetings turn into finished work, where to capture, when to add spaces and types, and what a productive day looks like.
Manage your context with spaces and typesHow items, spaces, and types fit together in Tana, when to reach for each, and how where something lives decides who on your team can see and work on it.
Build a shared issue tracker with a type - Tana Learn