#488 closed enhancement (fixed)
Ticket last modified
| Reported by: | anonymous | Owned by: | Jonas Borgström |
|---|---|---|---|
| Priority: | lowest | Milestone: | 0.9 |
| Component: | ticket system | Version: | 0.7 |
| Severity: | normal | Keywords: | |
| Cc: | manuzhai@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Would be nice to see when a ticket was last updated, number of times updated would be usefull to
Attachments (3)
Change History (14)
comment:1 by , 21 years ago
| Milestone: | → 0.8 |
|---|---|
| Priority: | normal → lowest |
| Severity: | normal → trivial |
comment:2 by , 20 years ago
| Severity: | trivial → enhancement |
|---|
comment:3 by , 20 years ago
| Component: | general → ticket system |
|---|
comment:5 by , 20 years ago
| Cc: | added |
|---|
comment:6 by , 20 years ago
| Milestone: | 0.9 → 0.8.1 |
|---|
Adding a patch. Note that it moves the ticket title down a little, to prevent it from unnecessarily wrapping because of the last modified date.
Maybe this could go in 0.8.1 after all?
comment:7 by , 20 years ago
| Milestone: | 0.8.1 → 0.9 |
|---|
- The patch
lastmod.diffappears to be incomplete. Only the CSS changes are included. - I'd rather see this go into 0.9, it's a totally non-critical enhancement. I'm not even convinced yet that adding this feature is a good idea.
comment:8 by , 20 years ago
I think that having both the created date-time and the last modified date-time displayed in the current verbose date format (e.g. Sat May 29 17:40:38 2004 for this ticket) looks way too cluttered.
As an alternative, I'll attach a screenshot that shows an alternative approach: both created date and last modified date are shown as relative times (ages). This conveys the information you really want most of the time in an easily readable format. If you need the exact date-time, you get that as a tool-tip over the relative time.
Comments?
by , 20 years ago
| Attachment: | ticket_lastmod.png added |
|---|
Screenshot of ticket display with relative times
Each change entry has its own timestamp, so technically you do have the information available already.
However, it's not a bad idea to maybe add a last modified timestamp to the 'yellow' area; Maybe below the creation date.