One of the most irritating things for me in testing is when you put some effort into a bug report, provide screenshots, find a way to record a screencast, give the steps and then… it gets marked as DUP
I generally check for keywords related to the bug first in the search. And if no report comes up, then mine is submitted. Otherwise, time of gathering videos, screenshots, and detailed steps goes into something already reported.
What approaches do you use for avoiding duplicate bugs?
What are your suggestions to promptly find an existing report?
Do you risk it, or do you continue to play it safe?
This often happens and especially in cross functional teams settings. However its completely fine. I understand the frustration.
Pro Tip:
Mark the ticket duplicate and close which has less details regardless when and by whom it was created.
Second, why putting a effort to first search if the ticket was already reported? If creating ticket does not cost - don’t spend time there. But yes if they cost:
What approaches do you use for avoiding duplicate bugs?
What are your suggestions to promptly find an existing report?
Depend upon the feature how old and popular it is / was? Was it tested before? Just simply search behind the keyword of the feature.
**
Do you risk it, or do you continue to play it safe?**
Not sure if I follow this, as I see no risk in there. Even if there is duplicate, close one
@ramanan49 I have raised duplicate bugs… but also note the root cause of bug reported often times i have seen it being different , in which case u can get it fixed in all the possible scenarios keeping both the bugs open
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.
I can feel you here.