What level/format of access should be given to a client to the issue tracking system?
- by dukeofgaming
So, I used to think that it would be a good idea to give the customer access to the issue tracking system, but now I've seen that it creates less than ideal situations, like:
Customer judging progress solely on ticket count
Developers denied to add issues to avoid customer thinking that there is less progress
Customer appointing people on their side to add issues who don't always do a good job (lots of duplicate issues, insufficient information to reproduce, and other things that distract people from doing their real job)
However, I think customers should have access to some indicators or proof that there is progress being done, as well as a right to report bugs.
So, what would be the ideal solution to this situation?, specially, getting out of or improving the first situation described?
