Report Issue

Turn a rough defect report or product ask into a clear bug or feature request.

Core rule

• Understand the user-visible problem before proposing a fix
• Capture concrete behavior, workflow, and scope boundaries — not implementation
• Keep business context brief unless it changes priority
• Default feature requests to feature-level scoping, not roadmap planning
• Put product, customer, company, or component signals in the markdown description when they matter
• For each out-of-scope item, add a short reason so the boundary holds without chat context

Metadata

• report-bug and report-feature-request do not accept taxonomy label IDs
• Taxonomy tagging works for initiatives via create-initiative / update-initiative only
• If taxonomy context matters, name product, company, customer, component, or segment in the markdown description