Raising duplicate bugs is not to be worried about unless every single one raised is a duplicate and its consuming too much time, effort for maintenance. Also if you or some else finds it as duplicate it can be closed as far as all the info is exactly the same.
What approaches do you use for avoiding duplicate bugs?
What are your suggestions to promptly find an existing report?
-
Scan through new bugs reported
-
Use the different filters, dashboards to find if it already exists
-
Communicate with team in calls-during a very busy deadline for a project we had to discuss the bugs on call and then raise them so it was easy for us to avoid duplicates as it was clear if it was already discussed and triaged there itself.
-
Remind the team to add all the mandatory fields like-feature/epic/story it is linked to, Environment, Severity, Reporter
Do you risk it, or do you continue to play it safe?
If I am confident the bug already exist and I can’t find it I will raise it and add comment ‘May be duplicate. Please close and link if duplicate is found’. I would not spend too much time finding it .Its always better to create a duplicate instead of miss. Sometimes it can be duplicate but the original issue was closed and fixed or moved to different board.