176145 - RFE: "jump to first unread comment", remember last displayed comment number per bug&user

Status: RESOLVED DUPLICATE of bug 1469023

(Bugzilla :: Creating/Changing Bugs, enhancement)

Description

[Vaclav Dvorak]

Bugzilla could remember which comment number was last the last time I displayed
a particular bug. Then, the next time I view that bug, it could provide a link
right at the top of the page pointing to the first unread comment. Also, above
that first unread comment, there should be some kind of visual separator.

Comment 1

[Dave Miller [:justdave]]

Wow, that would use up a LOT of space in the database remembering the last-read
comment number in every bug for every user....

Comment 2

[Vaclav Dvorak]

Yeah, I guess it might. Then again, I assume that the average user hasn't seen
more than just a few bugs. And this information could expire after a few months.
And if it's really such a big problem, the information could be stored in
cookies on the user's side. It loses the "portability" (as in "access from
anywhere", not "platform independence"), but at least it's something.

Comment 3

[Frédéric Buclin]

*** Bug 294413 has been marked as a duplicate of this bug. ***

Comment 4

[Stephen Lee]

Rather than last read comment number, it could store the last read date 
together with user_id and bug_id in a new table, expiring the oldest (whether 
after a maximum time interval or maximum number of bugs in the user's list or 
both).

This data structure would also lend itself well to a more up-to-date solution 
to bug 102571.


Ideally comments should be shown in batches too (some with literally hundreds 
of comments have a noticeable delay loading even on broadband), but I think I 
saw another bug about that somewhere.

Comment 5

[Jeff]

(In reply to comment #4)
> Rather than last read comment number, it could store the last read date 
> together with user_id and bug_id in a new table, expiring the oldest (whether 
> after a maximum time interval or maximum number of bugs in the user's list or 
> both).

You can still get the date and time of the comment if the last read comment is stored. If a more precise date is more useful to be stored when the bug was last viewed maybe that is a better solution. Using the fields that have been modified since that date could be emphasized somehow maybe making them bold.

Comment 6

[Jeff]

(In reply to comment #3)
> *** Bug 294413 has been marked as a duplicate of this bug. ***

I agree that the data storage issue shouldn't be a concern. In this case the usability outweigh storage concerns. Hard drives are cheap, a developers time is not.

Comment 7

[Preetam dwivedi]

Hello Iam new to bugzilla

Comment 8

[Kohei Yoshino [:kohei]]

This 16-year-old bug has been fixed recently on bugzilla.mozilla.org. The functionality will be available in the upstream Bugzilla 6 release. A screenshot can be found here: https://twitter.com/BugzillaUX/status/1012407513826783233

Comment 9

[Kohei Yoshino [:kohei]]

Closing as per my Comment 8. More enhancements are coming.

Comment 10

[Kohei Yoshino [:kohei]]

Just marking as a dup instead.