Difference between revisions of "The key ingredients of a good bug report"
m (moved How to Write Amara Bug Reports to The Key Ingrediens of a good Bug Report: Made the title more generic.) |
|||
Line 1: | Line 1: | ||
+ | ==Substance:== | ||
+ | 1. one-line summary | ||
+ | 2. URL | ||
+ | 3. What you expected vs. what actually happened | ||
+ | 4. How to make it happen again | ||
+ | 5. Screenshot | ||
+ | |||
+ | ==Style:== | ||
+ | 1. Use bullet points (not prose) | ||
+ | 2. Be concise | ||
+ | 3. Be specific | ||
+ | |||
[[File:Bugs01.jpg|400px|thumb|left|]] | [[File:Bugs01.jpg|400px|thumb|left|]] | ||
[[File:Bugs02.jpg|400px|thumb|left|]] | [[File:Bugs02.jpg|400px|thumb|left|]] |
Revision as of 10:53, 27 March 2014
Substance:
1. one-line summary 2. URL 3. What you expected vs. what actually happened 4. How to make it happen again 5. Screenshot
Style:
1. Use bullet points (not prose) 2. Be concise 3. Be specific