34 lines
1.1 KiB
Markdown
34 lines
1.1 KiB
Markdown
# AO And Discourse Issues
|
|
|
|
## Goal
|
|
|
|
Handle externally reported issues without misclassifying scope or over-claiming regression.
|
|
|
|
---
|
|
|
|
## Stable Patterns
|
|
|
|
- AO and Discourse reports are often incomplete or partially reproducible.
|
|
- External reports should be treated as external behavior until verified.
|
|
- Many issues only reproduce with authenticated users or in consumer-specific contexts.
|
|
- Some historical reports turned out to be service/configuration issues, environment issues, or existing behavior rather than new regressions.
|
|
|
|
---
|
|
|
|
## Investigation Rules
|
|
|
|
- Always clarify:
|
|
- authenticated vs non-authenticated
|
|
- reproducibility
|
|
- entry point
|
|
- whether the issue exists in main
|
|
- whether the behavior is external, existing, or regression
|
|
- Do not use vague comparison phrases like "same behavior" without scope.
|
|
|
|
---
|
|
|
|
## Historical Signals From Slack
|
|
|
|
- Historical reports around button visibility, analytics, slot updates, and consumer validation repeatedly required deeper reproduction work before scoping a fix.
|
|
- Slack history shows multiple examples where the original ticket or report was not enough to define the real root cause.
|