What you provide
- Your issue tracker
- A staging or test environment
- The original report
File it so engineering can act.
Document the issue, check for duplicates, and prepare a clear bug report.
Bug Reporter
A screenshot and "it's broken" costs engineering an hour of reconstruction. Half the time it is already filed.
Reproduces it in a safe environment and records the smallest path that triggers it
Captures the environment, version, console and network evidence
Searches the tracker for the duplicate before creating anything new
Writes the issue in your team's format, with the uncertainty labelled
File it so engineering can act
Document the issue, check for duplicates, and prepare a clear bug report.
Illustrative output. Your brief defines the result.What you provide. What you get back.
What you receive
Writes the issue in your team's format, with the uncertainty labelled
Review the output and its supporting context before deciding the next step.
See it in action.
A product walkthrough will show this task from brief to output.
Review boundaries
- Filing or commenting on an issue
- Anything touching production data
Available tools and actions are confirmed during workspace setup.
