This page contains tips for effective bug reporting in JIRA. Note that if Partners are using a different tool for project management, they should still follow the following recommendations as they are helping with easier bug fixing and smoother project delivery.
General info:
Bug reporting is a standard part of a project communication
It should be never taken personally - it is just about reporting a functional issue
Good bug reporting can help a lot with quicker bug fixing
Nobody can guarantee that the software is completely bug-free, so bugs are normal in IT projects
When:
during development phase - by QA Analyst or by customer project team
during UAT - mainly by customer UAT tester
Typical issues and how to fix them:
missing details about founded issue - typically how to reproduce the issue, data used for testing or detailed description
Possible solution: Follow the guideline and report bugs with all details
especially during UAT: what is reported is really not a bug, but more a suggestion for improvement, a question or just a misunderstanding because of not clear documentation
Possible solution: during the project - use project Stand-ups for discussing the behavior, discuss issues with UAT leader before reporting the bug
not reporting issues immediately
Possible solution: report founded issues daily, ideally before the tester is going home after testing
How to report a bug properly in JIRA:
Here is short documentation which should be shared with the customer. It will help to the customer to learn how to create bugs effectively.