Edgewall Software

Ticket #1735 (closed enhancement: fixed)

Opened 3 years ago

Last modified 21 months ago

Custom Query ''saved as'' Report.

Reported by: bruno@… Owned by: cboos
Priority: normal Milestone: 0.11
Component: report system Version: 0.8.4
Severity: major Keywords: query
Cc: bruno@…, dserodio@…, sdyson@…, s.lipnevich@…

Description (last modified by cboos) (diff)

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)

Attachments

Change History

  Changed 3 years ago by cboos

  • owner changed from jonas to cboos
  • priority changed from normal to low
  • status changed from new to assigned

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)

  Changed 3 years ago by anonymous

  • cc bruno@… added

  Changed 3 years ago by mgood

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.

  Changed 3 years ago by 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.

  Changed 3 years ago by dserodio@…

  • cc dserodio@… added

  Changed 2 years ago by cboos

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

  Changed 2 years ago by 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.....

  Changed 2 years ago by Armin Ronacher

I would just save the URL in the database. eg

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

  Changed 2 years ago by cboos

  • description modified (diff)
  • milestone set to 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.

  Changed 2 years ago by cboos

  • status changed from assigned to new

  Changed 2 years ago by sid

  • keywords query added

follow-up: ↓ 13   Changed 2 years ago by cboos

  • 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

in reply to: ↑ 12   Changed 2 years ago by sid

Replying to cboos:

* should make it possible to easily define and change the default custom query

See #2409.

  Changed 23 months ago by anonymous

  • cc sdyson@… added

  Changed 23 months ago by cboos

  • priority changed from low to normal

  Changed 22 months ago by cboos

  • status changed from new to closed
  • resolution set to fixed
  • component changed from general to report system
  • severity changed from normal to major

Implemented in r4782.

  Changed 22 months ago by anonymous

  • cc sdyson@… added; sdyson@… removed

  Changed 21 months ago by s.lipnevich@…

  • cc s.lipnevich@… added

Add/Change #1735 (Custom Query ''saved as'' Report.)

Author



Change Properties
<Author field>
Action
as closed
Next status will be 'reopened'
to The owner will change from cboos. Next status will be 'closed'
 
Note: See TracTickets for help on using tickets.