Modify ↓
Opened 17 years ago
Closed 17 years ago
#5763 closed enhancement (duplicate)
Custom Query does not support exporting of non-visible fields/columns to flat file
| Reported by: | Owned by: | Eli Carter | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | report system | Version: | |
| Severity: | normal | Keywords: | query |
| Cc: | nick+trac@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Whereas in the Report Module, you can write a query that will cause Trac to hide certain columns when it renders the HTML page, but make it available in the exported CSV or tab-delimited file, you cannot do this with the Custom Query module.
This is important to us, because we use a combination of Trac and Excel to manage tickets. While Trac is a great tool for storing tickets and querying information from the store, it's cumbersome to manipulate during meetings. Therefore, we export tickets to a file, with all the fields we need to discuss the tickets, and use Excel to manipulate it during meetings.
Attachments (0)
Change History (4)
comment:1 by , 17 years ago
| Cc: | added |
|---|
comment:2 by , 17 years ago
| Component: | general → report system |
|---|---|
| Keywords: | query added |
| Owner: | changed from to |
comment:3 by , 17 years ago
| Milestone: | → 0.11 |
|---|---|
| Owner: | changed from to |
comment:4 by , 17 years ago
| Milestone: | 0.11 |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
Actually see #2821.
Note:
See TracTickets
for help on using tickets.
In 0.11, you can actually select the columns you want to display in the custom query view, and they'll get exported using the alternate downloads.
(eli did the initial implementation, IIRC, reassigning to him)