Report Bug: follow up on an existing ticket (add a comment + logs) instead of always creating a new issue #486

New issue

Closed

opened 2026-10-06 12:58:40 +00:00 by sky_line · 1 comment

sky_line commented

2026-10-06 12:58:40 +00:00

Owner

Problem: every in-viewer Report Bug creates a new issue. Reporters who follow up (a retest, a fresh log, "still happening") create duplicates that we then have to merge by hand. Examples so far: #462 and #464 for the same problem; logs requested on #461 and on the crash retests (#402, #412, #465, #472, #473).

Proposal

Viewer (Report Bug window, LLFloaterReportBug):

Add an optional field: "Continuing an existing report? Ticket #", a number with an "Add to existing report" checkbox.
Fill it in automatically when the user arrives from a link we gave them, such as a secondlife:///app/reportbug?ticket=461 style SLURL or a website link. Also remember the last few tickets this install filed (stored locally) and offer them in a dropdown, e.g. "Follow up on #461: Custom alpha not applied after login".
When a ticket number is set:
- the summary becomes optional;
- the description is labelled "What's new since last time?";
- the log, screenshot and system info are attached as usual.

Relay (relay/slipstream_report_relay.py, website repo):

Accept an optional ticket field in the viewer and web reports.
If set and valid, add a comment to that issue (with the log and screenshot attachments) instead of creating a new one.
Validation:
- the issue exists and is open, or was closed recently (reopen policy to decide);
- the issue was created by the relay, or labelled from-viewer, so reports can't spam our internal tickets; or allow any issue but rate-limit;
- existing rate limits apply per ticket.
If the number is invalid, fall back to creating a new issue, and add a note "(intended for #N, which isn't accepting follow-ups)".
The comment header gives the source, version and system details like a new report, plus "Follow-up from the reporter".

Web report form (site/report.html): the same optional ticket-number field.

Our side: when we ask reporters for logs, include the ready-made follow-up link or instructions ("enter #461 in the Report Bug window").

Notes

Reporter identity isn't verified (no accounts). A follow-up is just a comment, so the risk is limited to noise. Keep the rate limits and the from-viewer restriction.
The relay already accepts unknown fields gracefully, so a new viewer field doesn't break old relays, and old viewers simply never send it.

**Problem:** every in-viewer Report Bug creates a new issue. Reporters who follow up (a retest, a fresh log, "still happening") create duplicates that we then have to merge by hand. Examples so far: #462 and #464 for the same problem; logs requested on #461 and on the crash retests (#402, #412, #465, #472, #473). ## Proposal **Viewer (Report Bug window, `LLFloaterReportBug`):** - Add an optional field: **"Continuing an existing report? Ticket #"**, a number with an "Add to existing report" checkbox. - Fill it in automatically when the user arrives from a link we gave them, such as a `secondlife:///app/reportbug?ticket=461` style SLURL or a website link. Also remember the last few tickets this install filed (stored locally) and offer them in a dropdown, e.g. "Follow up on #461: Custom alpha not applied after login". - When a ticket number is set: - the summary becomes optional; - the description is labelled "What's new since last time?"; - the log, screenshot and system info are attached as usual. **Relay (`relay/slipstream_report_relay.py`, website repo):** - Accept an optional `ticket` field in the viewer and web reports. - If set and valid, **add a comment to that issue** (with the log and screenshot attachments) instead of creating a new one. - Validation: - the issue exists and is open, or was closed recently (reopen policy to decide); - the issue was created by the relay, or labelled `from-viewer`, so reports can't spam our internal tickets; or allow any issue but rate-limit; - existing rate limits apply per ticket. - If the number is invalid, fall back to creating a new issue, and add a note "(intended for #N, which isn't accepting follow-ups)". - The comment header gives the source, version and system details like a new report, plus "Follow-up from the reporter". **Web report form (`site/report.html`):** the same optional ticket-number field. **Our side:** when we ask reporters for logs, include the ready-made follow-up link or instructions ("enter #461 in the Report Bug window"). ## Notes - Reporter identity isn't verified (no accounts). A follow-up is just a comment, so the risk is limited to noise. Keep the rate limits and the from-viewer restriction. - The relay already accepts unknown fields gracefully, so a new viewer field doesn't break old relays, and old viewers simply never send it.

sky_line added the

feature

priority

medium

labels

2026-10-06 12:58:40 +00:00

sky_line added this to the Slipstream project

2026-10-06 15:04:13 +00:00

sky_line added the

status

up-next

label

2026-10-10 04:53:28 +00:00

sky_line referenced this issue from a commit

2026-10-10 10:17:52 +00:00

Report Bug: follow up on filed reports, track their status (#486 #527)

sky_line commented

2026-10-10 10:54:57 +00:00

Author

Owner

Shipped and deployed on 2026-10-10. Report Bug > My Reports > Send follow-up adds a comment (plus optional log/screenshot) to a report you filed, authorized by the per-report receipt. Relay: /api/report/followup is live on starswirl. Viewer: commit 750736d2f5 + c617057cac. Filing, receipts and status were verified by the owner together with #527.

Shipped and deployed on 2026-10-10. Report Bug > My Reports > Send follow-up adds a comment (plus optional log/screenshot) to a report you filed, authorized by the per-report receipt. Relay: `/api/report/followup` is live on starswirl. Viewer: commit 750736d2f5 + c617057cac. Filing, receipts and status were verified by the owner together with #527.

sky_line

2026-10-10 10:54:57 +00:00