Anatomy of a ticket
A ticket is the unit of work in Starko: a customer report, a bug, a feature request or an internal task. This article walks through a ticket page from top to bottom so you know where everything is.
ticket detail
Header
The ticket number (for example 26-001011) is stable and searchable. The copy icon next to it copies a link.
The project chip shows which project the ticket belongs to. Click it to move the ticket.
The title is editable in place.
The chips under the title are the core fields: status, priority, assignee, team, collaborators and tags. Click any chip to change it.
Starko AI card
If Starko AI has worked on the ticket, a card shows the latest run: the pull request it opened, its risk level, whether CI passes and a one-line summary. View PR opens GitHub. Details opens the full session transcript. The Kind and Size selectors are how the ticket was classified (bug, improvement, feature; extra small to large), and Automated follow-ups lets Starko AI revise the pull request when a reviewer asks for changes.
Description
The description is a rich-text editor. Type / for headings, lists, code blocks, images and tables. Paste screenshots directly. Starko AI reads the description and attachments, so the clearer the steps to reproduce, the better the fix.
Watchers, relations and attachments
Watchers get notified on every change. Press Unwatch to stop.
Relations link tickets: blocks, blocked by, relates to, duplicates. Parent and child tickets show as sub-tickets.
Attachments holds files and screenshots. Agents can see them.
Comments and activity
The thread at the bottom mixes customer-facing replies, internal comments and the activity log. Internal comments are never sent to the customer. Mention @starko in an internal comment to hand the ticket to Starko AI, and mention a teammate with @ to notify them.
ticket detail full
The right sidebar
Development: the repository, branch and pull request. Fix with Starko AI starts a run.
Time: start a timer, add time by hand, set a reminder, a start date and a deadline. Time accrues per status, which Reporting uses.
Customer: the tenant, company and client the ticket is about. Click to link a record.
Custom ticket fields you define under Settings appear here too.
Creating a ticket
Press Create Ticket on any board column or list, or C on the tickets page. The dialog has the same chips as the ticket page plus the project selector and attachments. Give the ticket a verb-first title and put steps to reproduce in the body.
ticket create
Keyboard and shortcuts
⌘K then type the ticket number to jump to it.
/ in the description for the editor commands.
@ in a comment to mention a teammate or Starko.
Did this answer your question?