|
|
|
|
|
by eesmith
2229 days ago
|
|
Why do you have a giant list of potentially stale bugs? The policy described in the linked-to article is roughly equivalent to saying that every bug/issue must be passed to someone, who is in charge of that issue, including closing them. The main difference is that there's a single tracker instead of "personal workload lists". What happens to the workload on a personal list if the person is unexpectedly out of work for a month? Now that I've read a bit more: > Developers will only want to hear the same request so many times, before losing whatever is left of their sanity, and deciding to address the issue. What happens if the stakeholder's sanity runs out first? |
|
Most places I've worked have a bug log? Priorities balance between new feature development and fixing bugs / tech debt. If a bug isn't high priority, or the feature it was about has been changed or removed, the bug might now be stale - but still exists in a list somewhere.
> The policy described in the linked-to article is roughly equivalent to saying that every bug/issue must be passed to someone, who is in charge of that issue, including closing them.
It's the opposite, it's saying that if the bug / issue isn't easy enough to be solved right then, it needs to be reported again later, or added to the official prioritized road map.
> What happens if the stakeholder's sanity runs out first?
This is a good question :)