Tag Info

Hot answers tagged

10

I would always go for opening a new issue and linking it to the old one. The defect might look similar in its behavior, but its possible the cause is totally different. If possible let another developer fix this new issue. The added advantage of having one ticket with all the info is very slim, reducing the defect count is like giving management blindfolds, ...


3

You need to take a step back and look at the whole picture- why did the dev lead objected to the P0 setting ? It is not because "it is not in production" (well, it is but there is a higher level reason for that) but because the company doesn't have an agreed and accepted definition for priority levels across all teams.


2

As others have said, if there isn't a consistent definition of what constitutes top priority across all teams, there will be disagreement over what constitutes a top priority bug. That said, I have a few thoughts to offer: Will this bug break core functionality if it is introduced to production? If the answer is "yes" then priority should be higher. Does ...


2

I would open a new bug, and refer to the old one. I would also have a conversation with the development team about the duplication, more than just reporting the bug a second time. They might not have fixed the true root cause the first time, or you are doing something that they don't expect in your testing. A conversation could lead to better learning ...


1

Recently, I found a P0 bug in the pre-production environment. I am the lead QA and I refused the deployment in production before correction. The bug made a simple action not work (classical one, used by every single person of my company each day). The priority of a bug is not due to where or how it is found, but the severity and the effect of the bug. In ...



Only top voted, non community-wiki answers of a minimum length are eligible