make it easy to replace relative created date with absolute one

[rjbs]

I don't want to have to hover to see the actual date/time that a ticket was created. Please provide a simple way to replace that text with the actual creation date. (If relative date becomes the tooltip, that's fine. I won't care, because I won't hover!)

[anonymous]

I very much agree with this request. Sometimes one needs to know the exact date stamp of a ticket. The colloquial date reference is nice, but the exact date stamp is necessary. Maybe we could just have them both.

[Christian Boos]

In general, I find the colloquial date is much quicker to parse. Only this way can you immediately see if it's a matter of years, months or days. This is especially true when you have lots of dates like in the Change History or revision logs.

For the specific case of the ticket creation date however, it might indeed be useful to see the exact creation time at the first glance. This is however a trivial change to make in the local template, so I don't think it's worth making a configuration switch for this.

example customization:

ticket.html

@@ -132 +132 @@
         <div id="ticket" py:if="ticket.exists or preview_mode"
           class="${preview_mode and 'ticketdraft' or None}">
           <div class="date">
-            <p py:if="ticket.exists">Opened ${dateinfo(ticket.time_created)} ago</p>
+            <p py:if="ticket.exists">Opened <b>${format_datetime(ticket.time_created)}</b> (${dateinfo(ticket.time_created)} ago)</p>
             <p py:if="ticket.time_changed != ticket.time_created">Last modified ${dateinfo(ticket.time_changed)} ago</p>
             <p py:if="not ticket.exists"><i>(future ticket)</i></p>
           </div>

Proposing a wontfix, unless there's tremendeous support for the above change (those who have already voted for this can't vote again ;-) )

[Noah Kantrowitz]

+1 on wontfix. Not hard to make a plugin for this though (which would make it user-selectable, which I like better).

[sid]

+1 for wontfix on this.

[sid]

3 months and no further replies - seems like the wontfix-ers have it.

[anonymous]

I want absolute dates!

[black.box@…]

It would be nice to have the options for exact dates in the ticket history and the reports (created & modified fields).

[anonymous]

I would like exact dates please. And So do all my team - I have now ended up putting custom fields in so they can add the date manually.

[debacle@…]

It would be better to have ISO 8601 dates as default and the prosaic date as option. My colleagues and I prefer absolute dates.

[Christian Boos]

Note that it's now a user preference in 0.13 (try it there demo-0.13/prefs/datetime, change to absolute date format, then visit demo-0.13/log/trunk).

[Christian Boos]

(IIRC, that was done by jomae part of the extensive #2182 changes)

[framay <franz.mayer@…>]

Replying to cboos:

(IIRC, that was done by jomae part of the extensive #2182 changes)

Oh, I thought it was #9777, but nevertheless works fine in our installation with Trac 0.13dev-r10854

[Christian Boos]

#9777 rather - closing as duplicate would be more correct.

[debacle@…]

Replying to cboos:

example customization:

There is a problem with this approach. Having both the absolute date and the prosaic form together is too long for my taste. The absolute date, however, does not contain the link to the timeline. Instead, one has to change timeline/web_ui.py:

web_ui.py

@@ -241 +241 @@
         if data:
             def dateinfo(date):
                 return self.get_timeline_link(req, date,
-                                              pretty_timedelta(date),
+                                              format_datetime(date),
                                               precision='second')
             data['dateinfo'] = dateinfo
         return template, data, content_type

In the template, one still has to delete the obsolete "ago".