De-emphasize property changes in comment history
OK...already asked this but the issue was closed even after you asked for additional info. Here's a screen shot of what I'm talking about. While it's interesting to keep track of the changes in Tags and state - the comment 'Already works properly in 4.x BETA' is far more important than the tag changes. Most meta-data changes just aren't that important when reviewing the ticket. The current state of the metadata is important but the history of changes doesn't really add much value. It's strange that with so little actual value that they are emphasized so much. The default should simply be a one liner collapsed with 'Metadata-changes' that can be expanded if developers are interested. And multiple consecutive meta-data changes without comments should be rolled into one.
The discussion about the issue is the absolute most important part. The meta-data shouldn't get in the way.
-
6-10-2009_11-28-33_AM.jpg
45.7 KB
6-10-2009_11-28-33_AM.jpg
Discussions are closed to public comments.
If you need help with Lighthouse please
start a new discussion.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Will Duncan on 10 Jun, 2009 09:19 PM
I apologize about the issue being closed. I think I may have mistakenly resolved the issue and marked it as feedback while churning through backup up support request this morning. It was marked in the system though, and if you were to respond over email it would have reopened the ticket. We will need to check that in our support system.
Thanks for the extra details, I'll pass this along to the team,