How to solve miscommunication issues with qa in order to decrease task redundancy?
inna last edited by user
How to handle the situation where communicated bugs by the qa are duplicated as new issues by members of the project other than qa? What is the role if qa in this situation? Additional note: Time is limited, bug triage is impossible.
Without being flippant, this sounds like you've got a serious communication problem in the team.
Given the limited timeframe, here's a few things to consider:
- everyone in the team needs to know what a good bug report looks like
- everyone in the team needs to search for a bug report on the issue they're seeing before they write up a bug report. This means that bug report descriptions need to give a clear idea of the problem: I typically format my titles this way:
ModuleName:SubModule/PageName - ActionDescription produces ErrorDescription
- the bug reporting tool must have a good search function.
- anyone who finds a duplicate should link that duplicate to the original issue and close the duplicate.
If you can get everyone on the team doing this, it will help to reduce the number of duplicates created, and help to clear the number of duplicates active in the system without someone having to take the time for triage.
That said, despite the time constraints it's still important for someone to be performing bug triage to prevent time being lost. There's a saying in software that applies to your situation: "If you don't have time to do it right, you will have time to do it over." Not taking the time for bug triage guarantees that you'll be taking that much time or more doing the same things over and over for all the duplicate issues.