Your comments
We're wrapping up a few things now and then will brainstorm to determine priority.
10 year бұрын
This week or the next.
We have deployed another fix for this, please let us know if it solves the problem.
1. We will not add additional statuses, ever. I firmly believe that a good QA process can be conducted with the statuses we already have. As you rightfully pointed out, "there's a danger of having 'too many' status options." - so definitely, that's not happening.
2. Custom status is a hot topic internally. Carlos (CTO) wanted to do it due to high demand.
As stated above, I don't think Damn Bugs needs more statuses, I don't think it needs different nomenclature for the statuses we currently have, I think no one should need to customize the current statuses that we have, but obviously I'm not so grounded in my beliefs that I would turn a blind eye on user requests.
Clearly there's been enough demand to justify doing it, right now the issue is simply that it represents a lot of work and we have tons of other things we want/need to do, so we're prioritizing. It'll come.
Simon
2. Custom status is a hot topic internally. Carlos (CTO) wanted to do it due to high demand.
As stated above, I don't think Damn Bugs needs more statuses, I don't think it needs different nomenclature for the statuses we currently have, I think no one should need to customize the current statuses that we have, but obviously I'm not so grounded in my beliefs that I would turn a blind eye on user requests.
Clearly there's been enough demand to justify doing it, right now the issue is simply that it represents a lot of work and we have tons of other things we want/need to do, so we're prioritizing. It'll come.
Simon
Agreed
Customer support service by UserEcho
