Tus comentarios
Also check out Cloudhook, similar to Zapier. There are probably other tools out there for linking together services. This is a great way to mitigate the hassle of using a bunch of different websites.
Sounds good. This would be a good way to formally document the testing that a bug underwent.
I would find this useful, especially if I want to see everything except for one status. For instance, right now I want to view everything that's not Completed. This will involve me manually checking every checkbox except that one. I've added several statuses, so that's pretty annoying.
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!
Hear hear! I could definitely use a fifth option as well.
Yeah, that would be way clearer. I also had no idea that you were using Gravatar. Maybe even just make it clearer that that's what you're using, and a link to it or something?
Servicio de atención al cliente por UserEcho
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.