Write a Jira Bug Report From a Rough Description
Structure a vague complaint into a reproducible bug.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Write a Jira bug from this rough description: [ROUGH_DESCRIPTION]. Product area: [PRODUCT_AREA]. Environment details I know (browser, device, version, account type): [ENVIRONMENT]. Screenshots or logs I can attach: [ATTACHMENTS]. Write for a developer who has never seen the product. Produce a summary in the pattern '[Area] does X instead of Y when Z' under 100 characters that describes visible behaviour (not 'broken' or 'weird'); numbered steps to reproduce, one action each and the smallest set that still shows the problem (tell me which step you removed if you shortened mine); expected result; actual result; frequency (always, sometimes, once) if known; environment; workaround if any; impact in plain words; and a suggested priority with the reason, noting that the team decides. If I gave a version or start date, include it and ask whether it may be linked to a recent release, as a question and not a claim. Keep guesses about root cause out of the main text, as labelled hypotheses. List what is missing for a developer to reproduce the problem with follow-up questions for the reporter. Output Markdown for the description field, a one-line summary and suggested labels.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into ChatGPT, Gemini, Claude or another assistant.