No link to save custom queries

[trac@…]

According to [TracQuery] one should be able to save Queries by clicking the "Save Query" button, however there is no such button or link that I can find. Do I need to enable that feature somewhere? Or was it left out in 0.12

Thanks

[Remy Blank]

You need the REPORT_CREATE permission to save queries, as they are saved as reports.

[Christian Boos]

(see also #9617)

[tom@…]

Thanks! Did not know I needed to add REPORT_CREATE on top of TRAC_ADMIN.

[Christian Boos]

Really? If you have the TRAC_ADMIN permission, you should also have every other permissions. We could verify, but please first double check.

[tom@…]

I am doing everything as anonymous, with TRAC_ADMIN and the save query was not there. I had to add REPORT_CREATE to anonymous to get it to work.

[trac@…]

Also, after adding REPORT_CREATE I do get the Save Query button, but when I click that, I get the error message:

Error: Not Found No handler matched request to /report

[Christian Boos]

Ah, well, then it's something different: you simply disabled the trac.ticket.report.* modules. Check your TracIni#components-section.

[trac@…]

Well the [TracReports] page does say to:

[components] trac.ticket.report.* = disabled in order to remove the report completely, and use the TracQuery system

[trac@…]

Replying to trac@…:

Well the [TracReports] page does say to:

[components] trac.ticket.report.* = disabled in order to remove the report completely, and use the TracQuery system

I did try trac.ticket.report.ReportModule = disabled with the same result.

[Christian Boos]

But you'd have to enable it instead… You can't save a query if the reports module is disabled, as those queries are saved in the form of a report. Not perfect, we know.

One possible improvement would be to add a setting for disabling the creation and editing of SQL reports, which are the ones with the drawbacks mentioned in the TracReports page. The list of reports, the wiki syntax and the possibility to saves and edit the non-SQL queries would continue to work.

[Remy Blank]

(Mid-air collision)

I know it's an implementation detail, and users shouldn't have to know that, but saved queries are stored as reports, so if you disable reports, you can't have saved queries.

You should re-activate ticket reports, and if you want your users to go to the query page when clicking on "View Tickets", use the [mainnav] section to re-route the link (see TracInterfaceCustomization).

[trac@…]

Thanks that got it working!

[Christian Boos]

Keeping on the radar for the refactoring implied by comment:10.

I think we can make a generic trac.report module, with the usual api/model/web_ui files. The details of handling and rendering legacy SQL reports could stay in source:trunk/trac/ticket/report.py​ and source:trunk/trac/ticket/templates/

That way, it will be easy to disable trac.ticket.report.* and still have the report list of saved custom queries.

[Ryan J Ollos]

This ticket was largely a support issue, so I've created #12786 which clearly describes the proposed enhancement.