Checklist for publishing a good bug report:

1. Look for duplicates
2. Check for accuracy in all elements of the bug report
3. Role play as a different recipient (for example, a Test Manager) and ask if the bug report is really useful to them
4. Make a list of mistakes in the past with bug reporting and run it through the report
5. Check for attachments, their sizes and relevancy to the context of this bug report
6. Save a copy of your bug report in MS Word or other editors as everyone knows bug tracking systems, crash, too.
7. Assure that you spell check all of the text in the bug report – especially with bug title
8. Assure that the bug report contains good grammar and your word choice is clear to all who will read this bug report

More here.

Checklist for publishing a good bug report:

1. Look for duplicates
2. Check for accuracy in all elements of the bug report
3. Roleplay as a different recipient (for example, a Test Manager) and ask if the bug report is really useful to them
4. Make a list of mistakes in the past with bug reporting and run it through the report
5. Check for attachments, their sizes and relevancy to the context of this bug report
6. Save a copy of your bug report in MS Word or other editors as everyone knows bug tracking systems, crash, too.
7. Assure that you spell-check all of the text in the bug report – especially with bug title
8. Assure that the bug report contains good grammar and your word choice is clear to all who will read this bug report

More here.

Checklist for publishing a good bug report:

1. Look for duplicates
2. Check for accuracy in all elements of the bug report
3. Role play as a different recipient (for example, a Test Manager) and ask if the bug report is really useful to them
4. Make a list of mistakes in the past with bug reporting and run it through the report
5. Check for attachments, their sizes and relevancy to the context of this bug report
6. Save a copy of your bug report in MS Word or other editors as everyone knows bug tracking systems, crash, too.
7. Assure that you spell check all of the text in the bug report – especially with bug title
8. Assure that the bug report contains good grammar and your word choice is clear to all who will read this bug report

More here.

Checklist for publishing a good bug report:

1. Look for duplicates
2. Check for accuracy in all elements of the bug report
3. Role play as a different recipient (for example, a Test Manager) and ask if the bug report is really useful to them
4. Make a list of mistakes in the past with bug reporting and run it through the report
5. Check for attachments, their sizes and relevancy to the context of this bug report
6. Save a copy of your bug report in MS Word or other editors as everyone knows bug tracking systems, crash, too.
7. Assure that you spell check all of the text in the bug report – especially with bug title
8. Assure that the bug report contains good grammar and your word choice is clear to all who will read this bug report

More here.