Opened 20 years ago
Last modified 9 years ago
#642 new enhancement
RSS feed with all events for the tickets in a report
Reported by: | anonymous | Owned by: | |
---|---|---|---|
Priority: | low | Milestone: | unscheduled |
Component: | ticket system | Version: | 0.7.1 |
Severity: | normal | Keywords: | rss |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
To be able to track all changes of the tickets in the for example My Tickets report.
Attachments (0)
Change History (9)
comment:1 by , 20 years ago
comment:2 by , 20 years ago
Summary: | Timeline view (rss-feed) with all events for the tickets in a report → RSS feed with all events for the tickets in a report |
---|
Better summary.
comment:3 by , 20 years ago
Is there any chance of getting this one implemented? I'd love to do it myself but am a Python novice, and this strikes me as non-trivial for a n00b.
In #812 (marked as a duplicate of this) I suggest that reports should have two RSS links down the bottom of them - one for the normal report, one for the complete change history for that report.
This leaves the timeline as a neat and uncluttered view.
Regards, Brett
comment:4 by , 20 years ago
Currently I use the following report to accomplish something like this. It lists all changes to tickets owned by the current user, not very pretty to look at in trac, but sort of works as a rss feed.
SELECT p.value AS __color__, t.id AS ticket, summary AS _summary, field, c.time AS _changetime, c.author as _reporter, oldvalue AS old, newvalue AS new, newvalue AS _description FROM ticket t, enum p, ticket_change c WHERE t.time > strftime('%s', datetime('now', '-2 month')) AND t.status IN ('new', 'assigned', 'reopened') AND c.ticket = t.id AND p.name = t.priority AND p.type = 'priority' AND owner = '$USER' ORDER BY c.time DESC
comment:5 by , 18 years ago
Keywords: | rss added |
---|
comment:7 by , 18 years ago
Milestone: | → 2.0 |
---|
Getting all the changes for tickets assigned to a specific user will be possible with #1198.
Filtering by an arbitrary query or report would theoretically be possible, but probably costly.
comment:9 by , 9 years ago
Owner: | removed |
---|
#812 has been marked as duplicate of this ticket.