Steps
Use numbered actions. Include the starting state and the point where the problem appears.
Write the steps, the expected result and what happened instead. Add the environment and a recording link. Copy the report when it is ready.
## Title ## Steps to reproduce ## Expected result ## Actual result ## Environment ## Impact ## Recording link
Edits stay in this page. The template tool sends no form data to a server. Download the blank file works without JavaScript.
Use numbered actions. Include the starting state and the point where the problem appears.
Describe the intended result separately from the observed result.
Include the app version, OS and browser when known. State who is affected. Do not guess.
| Title | Screenshot selection controls remain visible after capture |
|---|---|
| Context | Screenshot selection and the recording review interface. |
| Observed | An inspected review screenshot contained stuck screenshot instructions. |
| Expected | Selection controls close before the screenshot result is delivered. |
| Development fix | Close selection windows before delivery and detach retired event handlers. The fix was validated locally; the development note did not report a public release. |
From our internal capture notes. The record covers the symptom and local fix, rather than a complete reproduction sequence.
Jira workflow · Linear workflow · Compare bug-reporting tools. Cloud AI drafts require Pro or Team.