Classificação do status
As fases do fluxo em que cada status da demanda se encaixa (Triagem, Em execução, Aguardando…): definem as seções do Kanban. As cinco do sistema vêm prontas; você cria as suas.
What you find on this screen
A portrait of the screen, read from the screen itself — it changes when the screen changes.
Form fields
Nome*Como a empresa chama esta fase do fluxo: "Em validação", "Aguardando cliente".
CódigoGerado do nome ao criar e fixo depois: é o que o status guarda. Nas telas e nas respostas, aparece o nome.
OrdemPosição da seção no Kanban: a menor vem primeiro.
CorCor do cabeçalho da seção no Kanban, em hexadecimal (ex.: #6366f1).
Do sistemaAs cinco do sistema não saem nem ficam inativas: o Tenka decide coisas por elas.
AtivaClassificação inativa some da escolha do status e do Kanban.
DescriçãoPara que serve esta classificação, para quem for escolher o status.
Start here
What the Status classification is for
Every request status belongs to a classification — the phase of the flow it sits in: Triage, In progress, Waiting, Done or Cancelled. The classification decides which Kanban section the status appears in and how Tenka reads the progress of the request. This screen is where you see the company’s classifications, change name, color and order, and create your own.
How to
How to create a classification
Tap New, give it a name (for example, In validation) and, if you like, pick a color. When you save, the classification gets its own code, taken from the name, which does not change afterwards: it is what the status stores internally. Screens, the Kanban and Tenkai answers always show the name. The new classification then appears in the choices of the Status classification field. To make it a Kanban section, open a request status and choose this classification in it.
Rules
The five system ones stay
Triage, In progress, Waiting, Done and Cancelled come ready in every company and cannot be deleted or deactivated: Tenka uses these five to decide things like moving the request when the timer starts. You can change their name, color and order. A classification that still has statuses cannot be removed either: change the classification of those statuses first.
Frequently asked questions
Why doesn’t my classification show up as a Kanban section?
A section only shows up when there is at least one active status in that classification — and, if the board is filtered by a workflow, at least one from that workflow. Open the status and check the Classification field. Also check that the classification is active and that the section was not hidden in the Kanban preferences.
I renamed a system classification: what happens to the statuses?
Nothing changes in the statuses: they store the classification code, which does not change, not the name. Only the section title on the Kanban, the label on screens and Tenkai answers start showing the new name.
What changed compared to the old status Category?
The Status category field is now called Classification and is no longer a fixed list of five values: it comes from this screen. Existing statuses keep the same classification, with nothing to redo. In spreadsheet import, the column accepts the name (In progress) or the code (EM_EXECUCAO), and the old Category header still works.
Classification, phase and status: which is which?
The status is the situation of the request, for example In testing or Waiting for customer. The classification is the phase of the flow that status fits into (Triage, In progress, Waiting, Finished, Cancelled or one you created) and defines the Kanban section. Phase is just a way to explain the classification: on screens, the name is always Classification.
Was this article helpful?
In the same module: Operations13
Ticket automations"When X, do Y" rules on tickets: assign, move, notify — without manual intervention.CalendarsWork schedule and holidays: the base calendar that defines business days, hours per day, and holidays (nation…TeamsWork teams with an owner and members — the basis for the team agenda, routing, and manager approvals.Roles and costsTable of roles (dev, QA, PM...) with cost and hourly rate — the feasibility ruler of the Studio.SLA policiesDefine response and resolution deadlines by priority/type — the clock that governs the tickets.Prioritization (WSJF)The backlog in the order the calculation recommends: value, urgency, and risk reduction add up to the cost of…Readiness (DoR/DoD)What needs to be resolved for a demand to ENTER a stage, and completed for it to LEAVE. It becomes a checklis…Squad roomsA room is a SLICE of the work plus that team's agreements. This is where it's decided what the big screen sho…
Tenka Academy
Explore the AcademyStep-by-step learning paths for your industry, inside the platform.