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?
