Record the steps, expected and actual results, then try to reproduce the bug. Give missing evidence its own branch with a review date, decide severity and priority, ask one person to accept it and have someone else repeat the original report before closing.
No account needed · Opens as your own editable page
Reports lose reproduction details, intermittent bugs stall and fixes close without a check against what the reporter saw.
Map a bug from report to verified fix, with rules for missing evidence, severity, priority, ownership and verification.
Keep observations and guesses apart in the report. Give an unreproduced bug its own branch and a review date. Verify the fix by repeating the original report under the same conditions.
Yes. Every label, box and line is editable, so replace the fictional example with your own screens and notes.
No. Open the template and edit it in your browser. Your work saves on this device. An account is optional if you want to sync your workspace.
Yes. Use Export in the editor to save a PNG, SVG or PDF, or download an editable .epicdraw backup.
List each journey the release could break, including recovery routes. · Attach evidence someone can open, covering essential dependencies. · Give each journey one owner and a response if it fails.
Preview and use template →
Write each end as what is true when the process stops. · Draw the usual route first and name who does each step. · Write each decision as a yes or no question and label every exit.
Preview and use template →
Write a focus question, not a topic. · List the concepts in a parking lot, most general first. · Put a verb on every link and check each arrow points the right way.
Preview and use template →
Write down who reads the chart and what they need to find. · List every post and the one post it reports to. · Check every box except the top one has exactly one solid line up.
Preview and use template →
Write the problem with a count and a period, and keep solutions out of it. · Rename the categories to fit the problem. · Add causes with the people who do the work, and ask why each one happens.
Preview and use template →
Write a central question with a target and a date. · Group a rough list of ideas into a few main branches. · Add detail only to the branches the answer depends on.
Preview and use template →