More often, I just simply add comment or update the bug details. I don’t see the need to write the new one if they have the same symptom but different location. This may help developers fix the problem thoroughly when they read your bug report.
Anyway, you can also check with your developers and see how they want to proceed this. Every team or developer is different. Follow process that make you and your team comfortable to follow.
Hope it helps
Hung
Normally, we should put the comment in the raised bug/or email to ask Dev whether this behavior is new one or duplicated one.
If, he said “enter new one” –> go ahead, else, just comment “please include this issue on bug resolution”
Hi Shweta,
More often, I just simply add comment or update the bug details. I don’t see the need to write the new one if they have the same symptom but different location. This may help developers fix the problem thoroughly when they read your bug report.
Anyway, you can also check with your developers and see how they want to proceed this. Every team or developer is different. Follow process that make you and your team comfortable to follow.
Hope it helps
Normally, we should put the comment in the raised bug/or email to ask Dev whether this behavior is new one or duplicated one.
If, he said “enter new one” –> go ahead, else, just comment “please include this issue on bug resolution”
Hope it works 🙂