Report a bug: title from the workspace and the reporter's words (#5377) (#5445)

* claim: #5377

* Report a bug: title from the workspace and the reporter's words (#5377)

With no dialog open the report was always labelled "Modeling" and its
summary pre-filled as "unexpected result", so every such report arrived
titled "Modeling: unexpected result" and the fallback to the first line
of "What happened?" never applied.

Label the report from the active workspace (Part, Sketch, Surface, Sheet
Metal, Plastic, Mesh, or Render), leave the summary empty so the title
becomes "<workspace>: <first line of the description>", and keep
"operation failed" when an error was recorded. The summary field now
hints that a short title is optional.

The triage script that asks for an empty in-app report to be pasted
recognises the new titles.
This commit is contained in:
raykholo
2026-10-25 03:03:08 +00:00
committed by GitHub
parent 1ceab2ed4c
commit dbe7dfa4bc
8 changed files with 50 additions and 9 deletions
+4 -3
View File
@@ -24,9 +24,10 @@ function fromApp(body) {
// Requests and plans, which aren't reproduced. Crash reports carry the crash folder's contents.
const NOT_A_BUG = /^\s*\[(feat|feature|change|enhancement)|feature request|suggestion|\?\s*$|^\s*(tracker|refactor|support|add|allow|crash|how|why|request|missing)\b/i;
// The app's report title. A long report opens the browser without its body and is copied to
// the clipboard instead (crates/ui-egui/src/issue_report.rs, draft_url), so an empty one wasn't pasted.
const APP_TITLE = /^[A-Z][A-Z ]+:\s*(operation failed|unexpected result)\b|^Modeling: unexpected result/;
// The app's report title: the open dialog (`EXTRUDE: …`) or the workspace (`Sketch: …`), then the
// reporter's summary. A long report opens the browser without its body and is copied to the
// clipboard instead (crates/ui-egui/src/issue_report.rs, draft_url), so an empty one wasn't pasted.
const APP_TITLE = /^([A-Z][A-Z ]+|Modeling|Part|Sketch|Surface|Sheet Metal|Plastic|Mesh|Render):\s*\S/;
// A report this long describes what it saw; only short ones are asked.
const SHORT = 300;
const ATTACHMENT = /user-attachments\/|\.solidcraft\b|repro\.json|\.(step|stp|3mf|stl)\b/i;
+2
View File
@@ -48,6 +48,8 @@ test('missing: short reports without steps are asked, with the version when it i
test('missing: empty app reports are asked to paste the copied report', () => {
assert.deepEqual(info.missing('EXTRUDE: operation failed', ''), ['paste']);
assert.deepEqual(info.missing('Modeling: unexpected result', ' '), ['paste']);
assert.deepEqual(info.missing('Sketch: line vanishes after trimming', ''), ['paste']);
assert.deepEqual(info.missing('Sheet Metal: operation failed', ''), ['paste']);
});
test('missing: reproducible, long, app-filed and non-bug issues are left alone', () => {
+2 -1
View File
@@ -59,7 +59,8 @@ const WORD_AREAS = [
const CRASH = /^\s*crash\b|\bpanic(ked)?\b|\bcaught panic\b/i;
const FEATURE = /^\s*\[?feature( request)?\]?\b/i;
// The in-app reports: `<COMMAND>: operation failed` / `Modeling: unexpected result`.
// The in-app reports of a failed command: `<COMMAND>: operation failed` (older ones also
// `Modeling: unexpected result`). Other in-app reports carry an `## Actual behavior` section.
const IN_APP_FAILURE = /:\s*(operation failed|unexpected result)\b/i;
function repoArgs(context) {