|
I agree, a lot of confusion comes arises from teh fact that the comment gets added to both issues.
If we add a comment only to one issue (the one the user is linking) would this solve the problem? Most people do not realise the comment is added to teh linked issue as well. Adding the comment to only one issue would fix one problem and add another. Although I think it's a good fix for some types of links. I don't know how many times I've linked a bug as a duplicate and how weird it looks on the dup bug to see the comment "dup of XYZ-123" when I'm looking at XYZ-123 right now. Still, that only is a problem on the duplicate link type. We have other link types (such as "is related to") which are symmetrical, and we would want the comments added in both places. Might actually work well to have a checkbox "symmetrical" on a link type that just sets both ends to be the same, and then only in that case would a comment added to a new link get added to both bugs. This would also solve the issue of having "is related to" being listed in the dropdown for linking a bug twice.
But I really think the best option is to tack on human-readable text so we get the full context instead of the simple "Comment by". It would solve a whole slew of other usability issues related to using the bugbase. Alternatively, make the "Change by" human-readable. The generic Field - Original Value - New Value is really hard to read. For example on this bug, there was a change by Anton today with three fields updated. Takes me a while to read all that with the table format. It would be so much more readable if it looked like this: Edited by Anton Mazkovoi [14/Jul/05 05:35 AM] For a resolved bug, something like: Resolved as By Design by Anton Mazkovoi [14/Jul/05 05:35 AM] Something like that. So the first line would be what happened, and lines after that would simply say in English what changed (similar to how the workflow editor prints field change tasks in English). It would be so much easier to read, and then I'd just leave my browser in "All" mode all the time. This is what MS's Product Studio does, and it's really nice and compact. Fair enough, I see what you mean.
Unfortuantely the 3.3 release is very close and we will not have time to implement this feature (adding comments to only 1 issue would be much simpler). Thanks for the suggestion. Anton |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Major
Comments provided when changing, linking or resolving an issue should be displayed next to the record of that action
And practically nobody uses the "All" view because it's so incredibly messy and hard to read.
What I'm suggesting is that we have something more human readable that combines all the info related to changes on the bugs in one compact place, so that the comments people add when they modify bugs have plenty of context so we know what they did as well as why. Right now we have to pick one or the other, or choose an overly verbose view.