Earlier quoted context omitted.
Actually a lot of people want it, especially the people who have to deal with the customer. The problem, as with most enterprise software, is that the desire for a feature often doesn't match reality. In my experience in services over the past decade and a half, most customers don't use these systems when they're available. They log in a couple of times at the beginning, and then they continue to rely on dealing with…
I agree with you my point was actually about his assertion that no one wanted it rather than that it would work. I/We now use email for client reporting/change requests which I then file into the bug system myself as many of our customers simply have no idea/want to use a bug tracker. I've yet to see one that works really well for end users (the best solution I've come up to is to have the file a bug button on each p…
I wanted to address his assertion as well, but thought it would be better as a child to yours than as a sibling.
>> I've yet to see one that works really well for end users
Yeah, this bit is very tricky. I would make the argument that your current approach might actually be one of the better approaches (at least from your customers' perspective).
In a lot of the engagements I've been involved with, end users just want their responsibility to end at "this didn't work", and for the developers/consultants to figure out what the user did that caused an issue themselves.
Reporting issues is work, and end users tend to be already busy with their own jobs. So the more work the end users have to do to report issues (i.e., filling out forms, taking screen shots), the more likely they are only going to report what they consider showstoppers.