Custom Query ''saved as'' Report.

[bruno@…]

That would be well if one could save a Custom Query as a new Report.

I think that that would make it possible to do without Create New Report…

---

See also: #1338 and #1594 (earlier requests for this feature)

[Christian Boos]

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:

• list of all the available reports in the obvious place (View Tickets)
• use of the {n} syntax for saved queries. The query can therefore be modified and all the references will use the latest version of the query (this is not the case with the !query: and [[TicketQuery]] forms)

[Matthew Good]

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.

[Ian Leader <__ian.leader__@…>]

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.

[Christian Boos]

My current thinking about this would be simply to save the query string in the sql field, not messing around with the actual SQL.

[anonymous]

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…..

[Armin Ronacher]

I would just save the URL in the database. eg

status=assigned&group=type&owner=cboos&type=enhancement&order=priority

[Christian Boos]

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.

[Christian Boos]

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