Ticket #97 (Duplicate)Sat Dec 02 12:34:07 UTC 2006
Need to be able to track tickets better
| Reported by: | Andrew Hodgkinson (6) | Severity: | Enhancement |
| Part: | Web site: Collaboa (bugs and subversion browsing) | Release: | 2nd public site release |
| Milestone: | 2nd public site release completed | Status | Duplicate |
Details by Andrew Hodgkinson (6):
Martin Avison pointed out in the Forum that it’s hard to track tickets. There’s no notification (e.g. by e-mail) of state changes so the ticket tends to just “vanish” as it goes into a fixed state.
Feature request: Some notification mechanism for changes in tickets.
Changelog:
Modified by Andrew Hodgkinson (6) Sun, December 10 2006 - 18:32:36 GMT
- Milestone changed from First public site release completed to Batch One code release completed
- Release changed from First public site release to Batch One code release
I don’t want to hold up the site release on this. For web site bugs we can live without the tracking I think. Once sources go up it’ll be more important to have tracking facilities somehow; hence, deferred to batch 1 code release.
Modified by Andrew Hodgkinson (6) Sun, December 10 2006 - 21:59:47 GMT
Note that one way to track ticket changes is using the RSS feed – see the links at the bottom of the sidebar on the right.
Modified by Andrew Hodgkinson (6) Fri, December 22 2006 - 15:29:58 GMT
After using the RSS feed myself for a while, I got annoyed at the way that ticket creation and ticket changes are merged. I’ve created new feeds that deal with these individually; see Changeset #164 for technical details. 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) Thu, January 18 2007 - 00:14:04 GMT
It would be nice if I could sort on the modified date; it gives a very quick view on which tickets have had comments added recently. :)
Modified by Steve Revill (20) Thu, January 18 2007 - 00:15:17 GMT
It’d also be nice if we could move this fault out of the Batch One milestone because it’s not really in any way a problem for that any more.
Modified by Andrew Hodgkinson (6) Fri, January 19 2007 - 09:27:44 GMT
- Milestone changed from Batch One code release completed to 2nd public site release completed
- Release changed from Batch One code release to 2nd public site release
You could’ve done that yourself, you know, Steve ;-)
Modified by Andrew Hodgkinson (6) Sun, March 25 2007 - 17:46:27 GMT
- Status changed from Open to Duplicate
The fault has changed topic to sorting on last updated time and therefore now duplicates Ticket #103.
