Ticket #103 (Fixed)Thu Dec 21 23:28:18 UTC 2006
Date of last update to ticket
| Reported by: | Steve Revill (20) | Severity: | Enhancement |
| Part: | Web site: Collaboa (bugs and subversion browsing) | Release: | 2nd public site release |
| Milestone: | 2nd public site release completed | Status | Fixed |
Details by Steve Revill (20):
It’d be nice if the tickets lists had a column which showed
the date at which a ticket was last modified – that’s often just as interesting/useful as knowing the date when the ticket was first raised.
Changelog:
Modified by Andrew Hodgkinson (6) Fri, December 22 2006 - 15:13:56 GMT
I’ve had a go at this in Changeset #163. Not closed yet because I don’t know if you really want to be able to sort using that column; that’s going to be relatively difficult to implement though. I’ve not looked into details but certainly the existing sorting mechanism assumes it is sorting on fields within the tickets table, rather than the ticket changes table, so some extension to that mechanism (or a wholly new sorting scheme) would need to be constructed.
Collaboa source tarball updated.
Modified by Andrew Hodgkinson (6) Fri, December 22 2006 - 15:28:48 GMT
Note Changeset #164 for further related developments. If you follow the “More feeds…” link at the bottom of the sidebar, you can access the relevant new RSS feeds.
Modified by Steve Revill (20) Tue, January 09 2007 - 16:36:03 GMT
It looks good to me. I see no reason why you shouldn’t want to sort
on the last modified date though – it’s a quick way to see what development
has been going on (if any).
Modified by Andrew Hodgkinson (6) Sun, March 25 2007 - 17:45:04 GMT
- Status changed from Open to Fixed
Due to the difficulties involved in adding this and due to Collaboa’s imminent upgrade to 0.6, I won’t implement sorting on the new column. There are ticket addition and ticket change RSS feeds available instead, which show in detail and in chronological order when things were changed. Adding a column sort would just duplicate features available by a different route.
For those that care: The sorting feature is tricky because all other columns in the view come from a particular table in the database, but the last updated time comes from elsewhere. The sorting mechanism inside Collaboa is tied strongly to columns coming from the one table only. It would need quite a few changes to cope with the idea of sorting on something from a different table entirely.
