#5298 closed enhancement (worksforme)
More time and date detail.
Reported by: | benw | Owned by: | Jonas Borgström |
---|---|---|---|
Priority: | lowest | Milestone: | |
Component: | ticket system | Version: | 0.10.3 |
Severity: | normal | Keywords: | ticket date time stamp datetime timestamp history |
Cc: | gt4329b@…, kirean@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
Hi, we have been using Trac for over a year now and I have always wondered why the original posting views do not show a date and time. Only the change history has this info. Instead of Opened 1 month ago or Opened 9 months ago, why not use the date and time as well as the time passed?
Attachments (1)
Change History (7)
comment:1 by , 18 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
comment:2 by , 17 years ago
Cc: | added |
---|---|
Keywords: | ticket datetime timestamp added |
I recognize that this is closed, but as there's still interest (on trac-users anyway) for a simple solution to this problem, I've provided a patch (against trunk r6046).
Once applied, add show_full_timestamp = true
to the [ticket]
section of trac.ini:
[ticket] ; other [ticket] settings... show_full_timestamp = true
by , 17 years ago
Attachment: | show_full_timestamp_r6046.diff added |
---|
follow-up: 5 comment:3 by , 16 years ago
Thanks for the patch. This is a non-trivial issue for us. We print tickets out for our histories, and exact dates are needed. the mouse-hover is a generally great solution for 99% of users. We just happen to be regulated, and need to be able to link a change in source, non-source, or a code comment date to an actual ticket change in some cases.
I am going to try it now.
comment:4 by , 16 years ago
Cc: | added |
---|
follow-up: 6 comment:5 by , 16 years ago
Replying to anonymous:
Thanks for the patch. This is a non-trivial issue for us. We print tickets out for our histories, and exact dates are needed. the mouse-hover is a generally great solution for 99% of users. We just happen to be regulated, and need to be able to link a change in source, non-source, or a code comment date to an actual ticket change in some cases.
I am going to try it now.
Works great. however, for some reason it breaks batchmodify plugin. Also, only those with TRAC_ADMIN can view tickets when this is enabled (my guess is only those with TICKET_ADMIN actually). Still turns out to be "OK" for my uses. I apply the patch when I need to do my printouts with timestamps. then I removed it for normal use again.
I will try to figure out why in the next few weeks.
comment:6 by , 16 years ago
Replying to anonymous:
Replying to anonymous:
Thanks for the patch. This is a non-trivial issue for us. We print tickets out for our histories, and exact dates are needed. the mouse-hover is a generally great solution for 99% of users. We just happen to be regulated, and need to be able to link a change in source, non-source, or a code comment date to an actual ticket change in some cases.
I am going to try it now.
Works great. however, for some reason it breaks batchmodify plugin. Also, only those with TRAC_ADMIN can view tickets when this is enabled (my guess is only those with TICKET_ADMIN actually). Still turns out to be "OK" for my uses. I apply the patch when I need to do my printouts with timestamps. then I removed it for normal use again.
I will try to figure out why in the next few weeks.
I should note, I pretty much blindly applied this to the latest 0.11 stable branch. at this time 0.11.5 r[8243]
That information is there… you have to move your mouse over it to see a tooltip appear.
That's not that obvious in 0.10, since you have no visual clue that you'll get the tooltip, but in 0.11, most of the date informations are links (back to the timeline), so you'd expect to get a tooltip.