Starko

Every ticket, every view,and where its fix stands.

Tickets hold the work your team and Starko AI do: customer problems, bugs, features and chores. See them as a board, list, table or Gantt, and see on each one whether a pull request is open or merged.

v2.starko.one/dashboard/tickets?view=…
Tickets
72%
My open ticketsCheckout bugsWaiting on reviewUrgent this week
Group Status Project is 🛒 Checkout redesign Filter Card fields Save view
Backlog14
low BacklogFeatureNo PR

Export invoices as CSV from the billing page

3d
low BacklogImprovementNo PR

Explain the empty state on the Orders page

5d
Open9
high OpenBugNo PR

Coupon field hides the order total on mobile

Northwind · Ana Kovač

Mia NovakNov 6, 20262h
medium OpenFeatureNo PR

Remember the last used payment method

Jon Reyes1d
In Progress4
urgent In ProgressBug Starko AINo PR

Address form loses focus after autocomplete

Northwind · Leo Brandt

Mia Novak4h
medium In ProgressBugPR #214

Attachments over 10 MB fail on ticket replies

Sara Lind1d
Closed128
medium ClosedBugMerged #207

Show VAT on the review step

Jon Reyes2d
low ClosedDocs

Typo in the password reset email

Sara Lind3d
At a glance

Tickets in short.

Layouts
Board, List, Table and Gantt, switched from the toolbar.
Group by
Status, priority, assignee, project, label, company, tenant or none.
Saved views
Private until you share them with the workspace. Tables keep their columns too.
Pull request chip
No PR, PR #n or Merged #n, on tickets in projects with a repository.
Statuses
Your own, each in one of five groups: Backlog, Unstarted, Started, Completed, Cancelled.
Custom fields
Text, Number, Yes / No, Date, Select, Multi-select and Member.
Work timers
One per person per ticket: start, pause, resume, stop, or add time by hand.
Admin only
Deleting tickets, exporting CSV, and editing statuses and fields.
Views

Four layouts over the same filters.

The Tickets page and every project page share one views engine. Switch between Board, List, Table and Gantt from the toolbar, group by any dimension, and add filters as chips. Filters live in the URL, so a filtered view is a link you can send. Save the combination as a view and it sits in a strip above the toolbar and under Tickets in the sidebar.
  • Drag a card into another group to change that value: status, priority, assignee, project or label.
  • Filters have typed operators for every built-in field, plus custom fields with operators that match their type.
  • Card fields picks what a board card shows. The table has its own column picker, and a saved view remembers both.
  • Right-click any ticket for Start Starko session (S), Archive (E) and Delete (⌫). The same menu works on Gantt bars.
  • Export CSV downloads the current filtered set. A view shows the first 500 tickets; narrow the filters to see the rest.
v2.starko.one/dashboard/tickets?layout=table
Tickets
72%
My open ticketsCheckout bugsWaiting on reviewUrgent this week
Group Status Project is 🛒 Checkout redesign Filter Columns Save view
TitleStatusPriorityAssigneeTagsDeadlineUpdated
Address form loses focus after autocomplete Starko AINo PR In Progress urgent Mia NovakBugNov 44m
Attachments over 10 MB fail on ticket repliesPR #214 In Progress medium Sara LindBugNov 71h
Coupon field hides the order total on mobileNo PR Open high Mia NovakBugNov 62h
Remember the last used payment methodNo PR Open medium Jon ReyesFeatureNov 201d
Show VAT on the review stepMerged #207 Closed medium Jon ReyesBugOct 302d
Export invoices as CSV from the billing pageNo PR Backlog lowUnassignedFeature3d
Start Starko session S
Archive E
Delete ⌫
Pull request state

See which tickets have a fix in review, and which are merged.

A ticket in a project with a linked repository carries a pull request chip on the board, list and table: a dashed No PR, a green PR #214 while it is open, or a violet Merged #207. A spinning Starko AI badge shows while a run is live. On the Gantt, bars are coloured by delivery state, with a strip and legend above the chart that count each one.
  • Delivery states: Merged, Done with no PR, PR open, and No PR yet.
  • When a Starko AI pull request is merged, its ticket closes and the merge is recorded on the run.
  • Support tickets outside code projects show no chip, so support views stay as they were.
  • The Gantt shows tickets with both a start date and a deadline. Drag from one bar to another to add a dependency, zoom in and out, or print it.
  • The run itself lives on the ticket. See Starko AI and review and merge.
v2.starko.one/dashboard/tickets?layout=gantt
Tickets
72%
My open ticketsCheckout bugsWaiting on reviewUrgent this week
Group Status Project is 🛒 Checkout redesign Filter Columns Save view
Merged1Done, no PR1PR open1No PR yet3
IssuesDuration
Closed
Show VAT on the review step5 days
Typo in the password reset email3 days
In Progress
Attachments over 10 MB fail on ticket replies8 days
Address form loses focus after autocomplete6 days
Open
Coupon field hides the order total on mobile7 days
Remember the last used payment method9 days
November 2026
23456789101112131415161718192021222324252627
100%
Show VAT on the review step
Typo in the password reset email
Attachments over 10 MB fail on ticket replies
Address form loses focus after autocomplete
Coupon field hides the order total on mobile
Remember the last used payment method
Ticket page

One page for the work, the customer and the fix.

A ticket's properties sit in one row of pills under the title: status, priority, assignee, team, collaborators and tags. Below are your custom fields, the description with a Starko AI tab next to it, the related conversation, SLA timers, watchers, sub-tickets, relations, attachments, comments and the activity feed. The side column holds what is about the work and the customer: Development, Time and Customer.
  • Development shows the repository with Fix with Starko AI and Start a session. A blue dot on the Starko AI tab means a run is live.
  • Sub-tickets show their progress, and a child shows Part of with its parent. Ask the ⌘L assistant to put one ticket under another.
  • Relations: Blocks, Blocked by, Duplicate of and Related to.
  • The creator and the assignee become watchers automatically, and collaborators join when added. Anyone can watch or unwatch.
  • Tickets on the Tickets and project pages open in a side sheet. Each ticket can also be exported as a PDF.
v2.starko.one/dashboard/tickets/6b3d…
Tickets/Ticket
72%

Address form loses focus after autocomplete

In Progress Urgent Mia Novak Web team CollaboratorsBugCheckout

Fields

Product areaCheckout
BrowserSafari 18
Customer impactBlocks purchase
Description Starko AI

On the shipping step, picking a suggested address moves focus out of the form. Buyers on Safari have to tap the ZIP field again before they can continue.

Reported by Leo Brandt at Northwind through the widget, with a session recording attached.

First response met Resolution due in 5h 20m
Watchers Unwatch
Part ofCheckout redesign: address step
Sub-tickets· 1 of 2 done
  • Reproduce on Safari 18 with a recorded sessionClosed
  • Add a focus test to the address formOpen
RelationsBlocksRemember the last used payment method

Development

northwind/web-app Fix with Starko AIStart a session

Time

00:42:13 Stop Logged 1h 20m Nov 2, 2026 Nov 4, 2026

Customer

Northwind Leo Brandt
Statuses and fields

Your statuses, your fields, and what it takes to close.

Statuses define the board columns. Each one belongs to a group that decides how it behaves: Completed and Cancelled set the ticket's closed date, and the groups drive time tracking and reporting. Custom fields appear on every ticket, can be shown only when another field has a value, and can be required before a ticket closes.
  • Workspaces start with Backlog, Open, In Progress and Closed. Rename, recolour, reorder, add your own or give one an emoji icon.
  • Deleting a status asks where its tickets should move.
  • Automation can auto-close tickets that have not been updated for a period you choose, and auto-archive tickets closed for a set number of months.
  • Require a resolution comment blocks closing until your team has described the fix. AI-review resolution quality scores the closing note from 1 to 5 with a tip.
  • Tags and assignment rules live in the same Tickets settings group, next to SLA policies and ticket workflows.
v2.starko.one/dashboard/settings/ticket-fields
Settings/Ticket fields
72%

Ticket fields

New field

Product area

Select6 optionsrequired to close

Browser

Text

Customer impact

Select4 options

Refund issued

Shown when Product area = Billing

Yes / No

Reviewer

Member

Closing requirements

What must be documented before a ticket can be closed.

Require a resolution comment

Closing is blocked until the ticket has at least one comment from your team describing the solution. The latest team comment is saved as the resolution.

AI-review resolution quality

After each close, Starko AI scores how well the closing note explains the cause and the fix (1 to 5), with a coaching tip.

Work timers

Time on a ticket, per person and per status.

Each person has their own timer on a ticket: start, pause, resume and stop from the Time card. Stopping asks which status the ticket moves to and for an internal comment on what you did. Closing a ticket with your timer running stops it in the same step. Time on this ticket breaks the total down by status, with time in status next to time worked.
  • Each status has a Timer switch. It is on for new statuses and off for completed and cancelled ones.
  • Add time records work done without a timer, in a format like 1h 30m. Entries can be edited or deleted.
  • The comment is optional, and required on every stop while Require a resolution comment is on.
  • Starko AI can start, pause and stop your timer from ⌘L, Home and Slack.
Create and fix

Open a ticket and start the fix in one step.

The create dialog has a Create and fix button that opens the ticket and starts a Starko session on it right away. Tickets also come in from the inbox, the widget, page errors, Improvements, workflows and the API, and each one lands on this same page.
  • Mention @Starko AI in a comment and it answers in the thread. It starts a run only when you ask it to.
  • Automate what happens to tickets with ticket workflows, and measure response times with SLAs.
  • Group tickets into projects to give them a repository and a timeline.

FAQAbout Tickets.

Keep exploring

Connect a channel and a repository. Turn the support queue into a build queue.

Feedback starts flowing in minutes. The first recommendation shows up as soon as a pattern repeats, and the first pull request as soon as you accept one.

Start for freeGet a demo