‣
Again, depends on team. If you have bug triage meeting, you can discuss opened bugs.
In some teams we discuss with developers. It is good if you have not big number of bugs.
While creating a big important things to keep in mind:
Before creating a defect check the requirements, did you understand them correctly.
- All fields must be filled in accurately and correctly.
- Describe what you tried to do, what did you expected, what did you get, tell about the environment you were working on.
- Description should be precise. Not like “The app sometimes converts some files incorrectly”, but specify exactly what.
- The report should be about app, not about criticizing someones work.
- Steps to reproduce the defect should be listed out. Screenshots or any attachments are good.
