Opened 15 years ago
Last modified 6 years ago
#8504 new enhancement
Named Custom Queries
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | unscheduled |
Component: | query system | Version: | 0.11.5 |
Severity: | minor | Keywords: | title bitesized |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
When running a custom query, customizing it further by adding filters, grouping, etc - the query is still a "Custom Query".
What I'd like is to have "named" or "saved" queries. Just saving a query is easy, you just add a link to a wiki page. But the headline still says "Custom Query" rather some real, readable, title.
Attachments (0)
Change History (8)
comment:1 by , 15 years ago
Summary: | Names Custom Queries → Named Custom Queries |
---|
comment:2 by , 15 years ago
Milestone: | 0.12 |
---|---|
Severity: | normal → minor |
follow-up: 4 comment:3 by , 15 years ago
I mean the actual queries, not TicketQueryMacro. And yes - a query_title=X parameter would do the job, at least partially (but see #8505). Is there such a thing that I missed?
comment:4 by , 15 years ago
Milestone: | → 0.13 |
---|
Replying to noamtm@…:
I mean the actual queries, not TicketQueryMacro.
Yes, it's probably better to restrict this to query: links.
And yes - a query_title=X parameter would do the job, at least partially
(but see #8505). Is there such a thing that I missed?
You probably missed the fact that there is already a way to save queries, together with a title and a description. But this feature has a few shortcomings:
- it requires the report module to be enabled (not a big deal, especially since you'd get the behavior requested in #8505)
- the user needs to have the proper permission in order to save a custom query as a report (REPORT_CREATE)
So I think the possibility to specify the title in a lightweight way as suggested here is useful: it would allow wiki editors to create links to nicer custom queries.
follow-up: 6 comment:5 by , 15 years ago
I'm thinking of temporarily changing the code on my site (as a patch) to support the title=X parameter. It should be easy, and I don't want to wait to 0.13. Can you point me to the correct place in code?
comment:6 by , 15 years ago
Replying to Noam Tamim <noamtm@…>:
I'm thinking of temporarily changing the code on my site (as a patch) to support the title=X parameter. It should be easy, and I don't want to wait to 0.13. Can you point me to the correct place in code?
Start at source:/trunk/trac/ticket/query.py@8368#L1035, there are two flavors of query: links (both should ideally support the query_title argument - maybe don't use title as that might conflict with existing custom fields).
That query_title should be shown as the "title" HTML attribute of the query:
link.
Then check the QueryModule.display_html
which already prepares the title
data.
Don't forget to share your patch so that the ticket can be closed much sooner than 0.13 ;-)
comment:7 by , 14 years ago
Keywords: | bitesized added |
---|---|
Milestone: | next-major-0.1X → unscheduled |
comment:8 by , 6 years ago
Component: | ticket system → query system |
---|---|
Keywords: | query report removed |
You mean having the possibility to add something like a query_title=… parameter to query: links or in the TicketQuery macro?
See also #1735.