Discount code accepted but total unchanged
/checkout?step=payment
High Medium AR
checkout
A board built for bug reports, not for sprints
Received → WIP → QA → Done, renameable per project. Severity and priority stay independent fields, so the same ticket is never argued about twice.
Included on Free · exports and integrations on Pro
The board's four stages, left to right: Received with 4, WIP with 3, QA with 2, Done with 6. The newest ticket, NT-248 — a discount code accepted but the total unchanged — sits at the top of Received, high priority, assigned to Ana Ruiz, with a screenshot and a recording attached.
How it works
1
Reports land in Received
Every new report enters the first status of the project's pipeline with its evidence already attached.
2
The team moves it through
Received → WIP → QA → Done, or the names your team already uses — statuses are project data, not a fixed list.
3
Done closes the loop
The reporter sees the status change from their portal link, and every move is written to the ticket's activity.
Severity is not priority
Technical impact and business urgency are separate fields, set side by side on the ticket and filtered apart — so a critical bug nobody needs this week does not have to be relabelled to be scheduled. Severity only appears on a card when it says something the priority did not.
Discount code accepted but total unchanged
Status
QA
Priority
High
Severity
Medium
Assignee
AR Ana Ruiz
Labels
checkoutIssues
linear ENG-1187 ↗ ✓Synced Sync now Unlink
Every move is also one call
The board's own menu and the move_ticket tool are the same operation, and the tool answers with the ticket it just moved. Parity is a rule here: a capability without its MCP tool is not finished.
Panel
WIP 1
Discount code accepted but total unchanged
/checkout?step=payment
High Medium AR
checkout
QA 2
Survey text overflows on mobile
/pricing
Medium AR
surveys
Widget launcher covers the cookie banner
/
Low DM
widget
MCP
> move_ticket ticket:"NT-248" status:"qa" { "ticket": { "id": "8f3a1d54-2b17-4c9e-9a20-6d5e0b71c433", "shortId": "NT-248", "type": "bug", "title": "Discount code accepted but total unchanged", "status": "qa", "priority": "high", "severity": "medium", "labels": [ "checkout" ], "rating": null, "assurance": "verified", "commentExcerpt": "The code applies but the order total never changes.", "pageUrl": "https://shop.example.com/checkout?step=payment", "assigneeId": "1c47b0e2-9d3f-4a68-8b51-72c0ad9e4f16", "hasScreenshot": true, "hasVideo": true, "dueAt": null, "archivedAt": null, "createdAt": "2026-08-26T09:12:44.118Z" } }
Exact behaviour
- Pipeline
- Received → WIP → QA → Done, renameable and reorderable per project
- Fields
- Severity (low, medium, high, critical) and priority (low, medium, high), independent and changed from the card itself
- Replies
- Public or internal, with reply templates
- Archiving
- Reversible; never deletes media or comments
- Plan
- Free and Pro · CSV export on Pro
- MCP tool
- list_tickets · move_ticket · comment_ticket · list_ticket_statuses
Works with
Questions teams ask before installing
Can I rename the columns?
Yes. Statuses are project data — names and order are configurable, and only the last one counts as completed. Tickets keep their history through a rename.
What is the difference between severity and priority?
Severity is technical impact and takes low, medium, high or critical. Priority is business urgency. They are stored and filtered separately on purpose.
What happens to tickets we no longer want to see?
Archive them. Archiving is reversible, excluded from default reads, and never deletes media or comments.
Put your next bug report on a board that fits it.
Free for one seat and five projects, pipeline included.
Start free Free plan · No credit card