One day I hope to find some place small that applies that by the 'book'.
My personal anecdote was, that no matter how much I tried to persuade the PM that it's a bad idea to put all the platforms (iOS, Web, Android, etc) stories and bugs into one giant tracker (Pivotal Tracker) we ended up doing that.... until the sudden realisation that it's a bad idea. It's hard to believe that PM had been on software projects before.
Found a typo in what is otherwise awesome writing, "loosing".
Why is this a problem as long as bugs are separated by component? Sometimes a feature will require work on multiple platforms, and it's nice to go to one place to get a sense of overall progress. And, since the bugs/tasks are separated by component, you can get the granular view you want as well.
You could get overall progress even with separated boards.
Overall progress doesn't help us who have to open/close/comment on them.
You wouldn't use a single issue tracker for five repos, how is this different?
Regardless, they wanted to switch once they realized how cluttered things became for non-devs as well.
One day I hope to find some place small that applies that by the 'book'.
My personal anecdote was, that no matter how much I tried to persuade the PM that it's a bad idea to put all the platforms (iOS, Web, Android, etc) stories and bugs into one giant tracker (Pivotal Tracker) we ended up doing that.... until the sudden realisation that it's a bad idea. It's hard to believe that PM had been on software projects before.
Found a typo in what is otherwise awesome writing, "loosing".