Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#37986 - {bugtracker} show timestap on bugs and their comments

Attached to Project: Arch Linux
Opened by Lazarus (Lazarus) - Tuesday, 03 December 2013, 06:00 GMT
Last edited by Dave Reisner (falconindy) - Friday, 28 March 2014, 11:19 GMT
Task Type Bug Report
Category Web Sites
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

I find it annoying and stupid that when browsing this bugtracker I have no way of telling when bugs were filed and when comments were posted. Being able to view such timestaps (e.g., "2013-12-3 14:59") provides valuable information in order to estimate how current the bugs and discussion are.
This task depends upon

Closed by  Dave Reisner (falconindy)
Friday, 28 March 2014, 11:19 GMT
Reason for closing:  Not a bug
Comment by Lazarus (Lazarus) - Tuesday, 03 December 2013, 06:02 GMT
Ugh. Great, I worded that completely wrong. The times are shown in the history tab it seems. My point still sortof stands though. Why isn't this information shown inline, say next to the username of the poster?
Comment by Gaetan Bisson (vesath) - Tuesday, 03 December 2013, 06:13 GMT
It is...

Above this bug report I read "Opened by Lazarus (Lazarus) - Monday, 02 December 2013, 20:00 GMT-10" and above your comment I read "Comment by Lazarus (Lazarus) - Monday, 02 December 2013, 20:02 GMT-10 — Edit — Delete".
Comment by Dave Reisner (falconindy) - Tuesday, 03 December 2013, 15:00 GMT
If you've ever gone to your preferences on this bug tracker, your browser probably filled in your username for the date format field and you hit 'OK' for something else, not realizing the error.

Loading...