Bug 190722 - Audibility issues (requiring comment or displaying history inline)
Summary: Audibility issues (requiring comment or displaying history inline)
Status: Closed FIXED
Alias: None
Product: Services
Classification: Unclassified
Component: Bug Tracker (show other bugs)
Version: unspecified
Hardware: Any Any
: --- Affects Only Me
Assignee: Bugmeister
URL:
Keywords:
Depends on: customtemplates
Blocks:
  Show dependency tree / graph
 
Reported: 2014-06-06 17:14 UTC by Bryan Drewery
Modified: 2014-12-21 17:53 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bryan Drewery freebsd_committer freebsd_triage 2014-06-06 17:14:19 UTC 
See Bug #190312

My last comment is "I'll take it.", following by the commit and now it is closed.

IMHO we should either require a comment or using the templates show the history inline.

As for showing history inline I think that makes a lot of sense given the history of gnats doing this.
Comment 1 Marcus von Appen freebsd_committer freebsd_triage 2014-08-22 19:29:44 UTC 
Can you be more precise about the expected behaviour?
Do you want a bug to require a comment on setting it to "Issue Resolved"?
Comment 2 Bryan Drewery freebsd_committer freebsd_triage 2014-08-26 18:34:03 UTC 
It's more of a bugzilla complaint I suppose. I am not familiar with its configuration and customization options much anymore.

https://bugs.freebsd.org/bugzilla/show_activity.cgi?id=190722

It would be really nice if the status changes from the activity showed inline in the comment section. It makes the discussion much easier to follow. GNATS was like this since each status change was effectively a comment.

I have this same problem at my $WORK as well. The discussion takes left turns for odd reasons which don't make sense until you see someone closed it in the activity history without leaving a comment about it.
Comment 3 Marcus von Appen freebsd_committer freebsd_triage 2014-08-26 18:48:40 UTC 
Besides the problem (to fix) of closing a bug without a comment, displaying the bug status next to a comment would be sufficient or between/after comments?

Is it only the bug status to see in a bug or other things, too? Would a quick link to the bug activity (show_activity?id=this_bug) also help?
Comment 4 Bryan Drewery freebsd_committer freebsd_triage 2014-08-26 18:58:03 UTC 
upstream discussion on it: https://bugzilla.mozilla.org/show_bug.cgi?id=11368
Comment 5 Bryan Drewery freebsd_committer freebsd_triage 2014-08-26 18:59:40 UTC 
There is a InlineHistory extension which achieves this. Example display shown here: http://globau.wordpress.com/2011/08/23/bugzilla-inline-history-extension/
Comment 6 Marcus von Appen freebsd_committer freebsd_triage 2014-08-26 19:12:57 UTC 
That does not sound too bad, especially, if it can be switched on and off within the user preferences.

http://bzr.mozilla.org/bmo/4.2/files/head:/extensions/InlineHistory/

seems to contain a reasonably up-to-date version, that's also used by bugzilla.mozilla.org. Worth to investigate and test.
Comment 7 Marcus von Appen freebsd_committer freebsd_triage 2014-12-21 09:33:17 UTC 
An inline history extension has been rolled out.
Comment 8 Bryan Drewery freebsd_committer freebsd_triage 2014-12-21 15:54:26 UTC 
(In reply to Marcus von Appen from comment #7)
> An inline history extension has been rolled out.

I was expecting to see 'status changed' on this comment but see nothing different so far.
Comment 9 Marcus von Appen freebsd_committer freebsd_triage 2014-12-21 17:53:57 UTC 
Please read the news on the front page. You can activate the history in your preferences.