By setting bugs to low by procedure, there's no longer a way of telling how several their consequences are.
This is specially important, because searches by importance no longer distinguishes bugs by impact. So the original purpose of importances is broken.
If a developer doesn't want to deal with reports with incomplete information, they are better served by filtering incomplete bugs. But the fact that a report has an importance of low doesn't tell them very much about if to look at it or not, as importance only shows order.
Moreover by setting importance only based in impact, once the reported sets status back to "confirmed" after providing the required info, the importance is simply correct instantly without anyone having to modify it. Doing the opposite will lead to critical bugs set as low, and nobody realising it.
@ Christopher M. Penalver
By setting bugs to low by procedure, there's no longer a way of telling how several their consequences are.
This is specially important, because searches by importance no longer distinguishes bugs by impact. So the original purpose of importances is broken.
If a developer doesn't want to deal with reports with incomplete information, they are better served by filtering incomplete bugs. But the fact that a report has an importance of low doesn't tell them very much about if to look at it or not, as importance only shows order.
Moreover by setting importance only based in impact, once the reported sets status back to "confirmed" after providing the required info, the importance is simply correct instantly without anyone having to modify it. Doing the opposite will lead to critical bugs set as low, and nobody realising it.