#1735 closed enhancement (fixed)
Custom Query ''saved as'' Report.
Reported by: | Owned by: | Christian Boos | |
---|---|---|---|
Priority: | normal | Milestone: | 0.11 |
Component: | report system | Version: | 0.8.4 |
Severity: | major | Keywords: | query |
Cc: | bruno@…, dserodio@…, sdyson@…, s.lipnevich@…, ohnobinki@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
Attachments (0)
Change History (19)
comment:1 by , 19 years ago
Owner: | changed from | to
---|---|
Priority: | normal → low |
Status: | new → assigned |
comment:2 by , 19 years ago
Cc: | added |
---|
comment:3 by , 19 years ago
Well, cmlenz has been planning to phase out the Reports module for a while now, so let's not start planning new features around it. Plus, turning one of the queries into a SQL report loses a lot of the flexibility that the query module offers. If we provide a button to save the query I think that it needs to save it for use in the query module, not as SQL.
comment:4 by , 19 years ago
Are details of the proposal to remove the report module available somewhere? I agree that it would be better to focus effort on the query module (including the ability to save queries as queries, not reports), but I would hate to lose the flexibility of the report module.
comment:5 by , 19 years ago
Cc: | added |
---|
comment:6 by , 18 years ago
My current thinking about this would be simply to save the query string
in the sql
field, not messing around with the actual SQL.
comment:7 by , 18 years ago
IWBRN nice be able to save custom queries somehow. We also need the ability to select which fields are in the output.
just my 2 cents…..
comment:8 by , 18 years ago
I would just save the URL in the database. eg
status=assigned&group=type&owner=cboos&type=enhancement&order=priority
comment:9 by , 18 years ago
Description: | modified (diff) |
---|---|
Milestone: | → 0.11 |
This feature seems to be requested quite often. I propose to add a Save Query button in the Ticket Query page when the user has the REPORT_CREATE permission. This would then go to the new report page, with the query field pre-filled with the query string (as mentioned above).
The report module could first handle both SQL queries and custom queries, then later (milestone:0.12?), support for SQL queries could be dropped from the report module.
comment:10 by , 18 years ago
Status: | assigned → new |
---|
comment:11 by , 18 years ago
Keywords: | query added |
---|
follow-up: 13 comment:12 by , 18 years ago
Description: | modified (diff) |
---|
If a query is saved as a report, then it can be easier to tweak it further, even if the UI for that is not (yet) available in the Custom Query view:
- specify which columns should be displayed (#2821)
- should make it possible to easily define and change the default custom query
comment:13 by , 18 years ago
comment:14 by , 18 years ago
Cc: | added |
---|
comment:15 by , 18 years ago
Priority: | low → normal |
---|
comment:16 by , 18 years ago
Component: | general → report system |
---|---|
Resolution: | → fixed |
Severity: | normal → major |
Status: | new → closed |
Implemented in r4782.
comment:17 by , 18 years ago
Cc: | added; removed |
---|
comment:18 by , 18 years ago
Cc: | added |
---|
comment:19 by , 13 years ago
Cc: | added |
---|
That's an often requested feature. The usual answer has so far been: copy the query URL and paste it in a Wiki page after a
query:?
link or inside a [[TicketQuery]] macro.However, I'd like to investigate the possibility to use the current query's SQL as a basis for creating a new report, as you suggested.
The advantages: