A bug report template you can use.

Write the steps, the expected result and what happened instead. Add the environment and a recording link. Copy the report when it is ready.

Download for macOS See the free plan

Fill in what you know.

Your report

## Title


## Steps to reproduce


## Expected result


## Actual result


## Environment


## Impact


## Recording link

Make the next person’s first check obvious.

Steps

Use numbered actions. Include the starting state and the point where the problem appears.

Expected and actual

Describe the intended result separately from the observed result.

Environment and impact

Include the app version, OS and browser when known. State who is affected. Do not guess.

Make the report reproducible.

Check before sharingGive the starting stateName the screen, account state or settings needed before the first action.Separate expected and actualState what should happen and what you observed. Keep the two fields distinct.Add known contextInclude relevant versions, impact and a recording link. Leave unknown facts unfilled.

One issue from our own capture work.

Historical example from Moonshot’s screenshot work, September 10, 2026
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.

Keep the visual evidence beside the report.

RecordShow the steps and narrate the issue

DraftWrite the report or review an AI draft

AttachLink the recording in Jira or Linear