Support

Prepare clear issue context without exposing private work data.

Support starts with the product name, version, workflow area, and a short description of what the operator expected to happen. Review any exported diagnostics before sharing them outside an authorized channel.

Report details

Useful context for a support review.

Product name and version.
Workflow area, such as request creation, trace review, lookup, cache, or release package.
Visible diagnostic message or status text, rewritten if it contains private details.
Whether the issue repeats after reopening the desktop tool.

Screenshot and support-bundle privacy checklist

Review before sharing.

Do not share real workbook names, client names, project references, welder records, internal paths, screenshots, or private release links through a public channel.

Issue report template

Copyable structure for a clean first report.

Product:
Version:
Workflow area:
Expected result:
Actual result:
Visible status or diagnostic, rewritten if needed:
Repeatable after reopening:
Screenshot attached: yes/no, privacy reviewed first
Support export attached: yes/no, privacy reviewed first

Private boundary

Sanitize evidence before it leaves the authorized path.

Remove or rewrite workbook names, project names, client names, and internal paths.
Do not include real welder identifiers or work package references in public reports.
Prefer plain-language reproduction steps over raw screenshots when data cannot be sanitized.