Ticket statuses, fields and tags
Three settings shape every ticket in the workspace: statuses define the board columns and what counts as done, ticket fields add the data your team needs, and tags label tickets for routing, filtering and reporting. All three are under Settings.
Ticket statuses
Settings → Ticket statuses lists your statuses in board order. Each has an icon, a name, a group and a colour.
settings statuses
Group is what matters for automation: Backlog, Unstarted, Started, Completed or Cancelled. Time tracking runs in Started statuses; Completed and Cancelled count as closed in Reporting and in SLAs.
Timer switches per-status time tracking on or off.
Default marks the status new tickets get.
Drag the arrows to reorder; the board follows.
Below the list, Automation closes tickets that have not been updated for a period you choose and archives closed tickets after another period. Both run daily and appear as "Automation" in the ticket's activity.
Ticket fields
Settings → Ticket fields adds custom fields that appear in the ticket sidebar and can be shown on cards, filtered on and exported.
settings ticket fields
Field types include text, number, date, single and multiple choice, checkbox, URL and person. Mark a field as required to ask for it when a ticket is created. Fields can be limited to a project.
Tags
Settings → Tags holds the labels you attach to tickets. Create a tag for a customer, an area of the product or a kind of work.
settings tags
Tags do real work in Starko:
Assignment rules route by tag.
Filters, groups and saved views use tags.
Starko AI uses the repo-learnings tag for the notes it files after a run.
Reporting breaks tickets down by tag.
Recommended starting set
Statuses: Backlog, Open, In Progress, In review, Closed, Cancelled.
Fields: Severity (choice), Affected version (text), Customer impact (choice).
Tags: one per product area, plus billing, bug, feature-request.
Did this answer your question?