Modify ↓
Opened 15 years ago
Closed 15 years ago
#8225 closed defect (fixed)
Exporting report to CSV and tab-delimited file: Missing page argument
| Reported by: | Owned by: | Christian Boos | |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.12 |
| Component: | report system | Version: | 0.11-stable |
| Severity: | normal | Keywords: | query export page CSV tab-delimited |
| Cc: | esmith@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
- When I try to export a report to a CSV or tab-delimited file I always get the first page of results (100 tickets) even when viewing later pages
- The page argument seems to be missing from the link for downloading in these other formats
- The page argument doesn't apply to the 'RSS Feed' and 'SQL Query' links
Attachments (0)
Change History (5)
comment:1 by , 15 years ago
| Keywords: | query added; report removed |
|---|---|
| Milestone: | → 0.11.5 |
| Severity: | trivial → normal |
comment:2 by , 15 years ago
| Owner: | set to |
|---|
comment:3 by , 15 years ago
| Status: | new → assigned |
|---|
Strange, now I see the opposite… works fine for custom queries and not for reports, I must have tested a saved query ;-)
The ReportModule._render_view method really needs a big clean-up, btw.
comment:4 by , 15 years ago
| Milestone: | 0.11.6 → 0.12 |
|---|
Actually, the paging for the CSV format in reports was explicitly turned-off in r7307.
For queries, it depends whether we selected an explicit limit or not (r7308).
So I think reports should behave like custom queries: have CSV format contain all the results, unless an explicit max has been set, in which case paging should be fixed.
I'll implement that on trunk where one can already set the max number of results for a report.
Note:
See TracTickets
for help on using tickets.
Duplicate of #7396.
I verified that this works fine with reports, but it seems that it doesn't (anymore?) for custom queries.