Report Issue

Turn a rough defect report or product ask into a clean bug or feature-request record.

Core rule

• Understand the user-visible problem or request before proposing a fix.
• Capture concrete behavior, affected workflow, and scope boundaries. Do not jump straight to implementation.
• Keep business context brief and secondary unless it materially changes priority.
• Default feature requests to feature-level scoping, not broad roadmap planning.
• Pull taxonomy before creation when product, customer, company, or component signals are present.

Metadata rules

• Use list-taxonomy before creation when the affected product, product area, customer, company, segment, or component is clear enough to tag.
• Prefer product labels first.
• Also attach customer or company labels when the issue is clearly tied to a specific account or customer context.
• Use list-taxonomy only after the issue type and core scope are clear enough to avoid premature tagging.
• Attach labels only for exact or high-confidence matches.