+8
Voltooid
Add priority field within bug details
some time severity is not the most important thing to organize my work list depending on it
there would be bugs with minor severity but for company reasons it's necessary to resolve this bug over other ones even if they have higher severity.
Thanks.
there would be bugs with minor severity but for company reasons it's necessary to resolve this bug over other ones even if they have higher severity.
Thanks.
Customer support service by UserEcho
Hear hear!
I take Severity to mean the scale of the bug: how, well, severely it takes the app down. Is it a typo, or is a 500 when you try to do a fundamental activity in your application? Naturally, developers always want to fix the more severe bugs first.
On the other hand, Priority is how much the actual customers of the application (whether that's end-users or corporate management) want the bug to be fixed. As Mateo said above, a typo on the front page is not severe at all, but it's pretty important to take care of right away!
Thanks for listening and for this fantastic, free, functional software!
With further thought, I think what we might actually be wanting is a Priority (how important is it to do this right now), and something like Estimated Difficulty (how long will this take to do) or Scale (how much of a project is this vs a minor bugfix).
My previous take on Severity was not quite right. If you're getting a server error when you try to do something fundamental, that's probably pretty high priority as well as high severity. So that's not a good example.
However, a rather large project might be considered high severity because it will take a lot of effort, but it might be considered low priority because there's a lot of smaller things that management would like to have cleaned up first. So, some granularity when prioritizing tickets would be useful.
Please add priority field. Bug report looks incomplete without it.
This field is badly required for bug tracking please add it.
We're adding this today.
Woohoo!
Great!
This is now live. Please give it a try and let us know if you find any bugs. Thanks!