Opened 19 years ago
Last modified 5 years ago
#3370 new enhancement
Custom query RSS feed differes from CSV, Tab files
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | high | Milestone: | unscheduled |
| Component: | ticket system | Version: | 0.9.4 |
| Severity: | normal | Keywords: | |
| Cc: | Thijs Triemstra | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
The RSS feed for a custom ticket query does not contain same fields as what the CSV and Tab Separated files do. The following important fields appear to be missing from the RSS feed: owner, type, priority, mileston and resolution.
Attachments (0)
Change History (10)
comment:1 by , 19 years ago
| Component: | general → ticket system |
|---|---|
| Milestone: | → 0.11 |
comment:2 by , 19 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:3 by , 19 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
follow-up: 8 comment:4 by , 18 years ago
This seems most applicable to the report feed. How should we do this? I'm a bit fond of adding a trac namespace and providing them as custom xml elements, however I don't know of any widespread readers that support rendering such things. Should we add it as part of the description then?
follow-up: 6 comment:5 by , 17 years ago
| Milestone: | 0.11-retriage → 1.0 |
|---|---|
| Type: | defect → enhancement |
I'd say that this is an enhancement, not a defect. Retargeting.
comment:6 by , 16 years ago
Replying to rblank:
I'd say that this is an enhancement, not a defect. Retargeting.
comment:8 by , 15 years ago
| Cc: | added |
|---|
Replying to thatch:
Should we add it as part of the description then?
What abou adding a similar table as you see in the ticket notification email to the description with those missing fields?
comment:9 by , 15 years ago
| Cc: | added; removed |
|---|
comment:10 by , 10 years ago
| Owner: | removed |
|---|---|
| Status: | reopened → new |
Don't close tickets without a comment.