Edgewall Software
Modify

Opened 17 years ago

Closed 16 years ago

Last modified 12 years ago

#1735 closed enhancement (fixed)

Custom Query ''saved as'' Report.

Reported by: bruno@… 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 Christian Boos)

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 (0)

Change History (19)

comment:1 by Christian Boos, 17 years ago

Owner: changed from Jonas Borgström to Christian Boos
Priority: normallow
Status: newassigned

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)

comment:2 by anonymous, 17 years ago

Cc: bruno@… added

comment:3 by Matthew Good, 17 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 Ian Leader <__ian.leader__@…>, 17 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 dserodio@…, 17 years ago

Cc: dserodio@… added

comment:6 by Christian Boos, 16 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 anonymous, 16 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 Armin Ronacher, 16 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 Christian Boos, 16 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 Christian Boos, 16 years ago

Status: assignednew

comment:11 by sid, 16 years ago

Keywords: query added

comment:12 by Christian Boos, 16 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

in reply to:  12 comment:13 by sid, 16 years ago

Replying to cboos:

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

See #2409.

comment:14 by anonymous, 16 years ago

Cc: sdyson@… added

comment:15 by Christian Boos, 16 years ago

Priority: lownormal

comment:16 by Christian Boos, 16 years ago

Component: generalreport system
Resolution: fixed
Severity: normalmajor
Status: newclosed

Implemented in r4782.

comment:17 by anonymous, 16 years ago

Cc: sdyson@… added; sdyson@… removed

comment:18 by s.lipnevich@…, 16 years ago

Cc: s.lipnevich@… added

comment:19 by ohnobinki@…, 12 years ago

Cc: ohnobinki@… added

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Christian Boos.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from Christian Boos to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.