Discount code accepted but total unchanged
/checkout?step=payment
The person who reported it gets a link that opens on every ticket they filed. The client paying for the work gets a key of their own and sees the whole project. Neither of them signs up.
Included on Free and Pro
A render of the reporter’s portal, branded as the customer’s own product. It shows report NT-248 at stage Received, the team’s public reply, a box to answer back, and a note that three other reports from the same person are on the page. No account is involved.
1
A reporter link comes from a ticket's menu in the panel, or from the create_reporter_portal_link MCP tool. A named client access is added per person and hands you their key once.
2
No password and no seat. For a reporter the link is the credential; a client types a ten-character key, drawn from an alphabet with no O/0 and no I/1 because somebody reads it out loud.
3
Status changes and public replies appear on the same page, so nobody has to write “any update?” again.
Your side of the same report is the whole evidence bundle: the annotated screenshot, the recording, the console and network cluster, the environment. Only the comments explicitly marked public cross to the portal, and that split is a predicate in the query rather than a filter in the interface. Whether the screenshot and the recording travel with them is a switch, per project.
A render of the ticket drawer in the panel. Ticket NT-248, “Discount code accepted but total unchanged”, is a bug of medium severity reported five minutes ago, and the header carries the MCP command that opens it, get_ticket NT-248. The report from Marta Oliva arrived with an annotated screenshot of the checkout — a red box drawn around the SPRING24 code and an arrow at the order total, marked “total unchanged” — a forty-two second screen recording, and a cluster of nine console and network entries captured in the twenty-two seconds before she sent it, among them a failed POST to /api/cart/discount and an uncaught TypeError. Below the report the drawer lists the environment it happened in: Chrome 128 on macOS, a desktop at 1512×982 with a 1280×712 viewport.
There is nothing to copy across and nothing to keep in step. The reporter's page shows the stage the ticket is in on your board, in the project's own language, the moment it moves.
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.
No. The portal is a link scoped to that reporter's own tickets. Reporters never sign up and never occupy a seat on your plan.
No. Every comment is stored with a public or internal visibility, and the portal renders the public ones only.
Both. The portal is a per-project setting — on or off, its language, whether a client access sees every ticket or only the marked ones, and whether screenshots and recordings travel with them. It is changed in the panel or with the set_client_portal MCP tool, and a single client's key is revoked without touching anyone else's.
The reporter portal is included on the Free plan.