Opened 19 years ago
Last modified 10 years ago
#2465 new enhancement
Add "custom query" functionality for changesets
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | next-major-releases |
Component: | version control/changeset view | Version: | none |
Severity: | critical | Keywords: | query changeset tracobject |
Cc: | guillaume.tardif@…, vyt@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
I think it would be really useful to have the ability to quickly define queries on changesets, similarily to what can be done on tickets (ie. with a GUI allowing filters on changeset comments, author, file path and commit dates).
This page should also implement RSS feed (as Ticket custom queries), to allow notification of specific changes.
I suppose that the implementation would be similar to the ticket 'custom query' page (but I havn't looked in depth at the code, not being a Python developer… yet). I leave it to the TRAC people to set milestone, priority, etc. Many Thanks for this great software BTW.
Attachments (0)
Change History (7)
comment:1 by , 19 years ago
Keywords: | tracobject added |
---|---|
Owner: | changed from | to
comment:2 by , 19 years ago
Cc: | added |
---|
comment:3 by , 19 years ago
Cc: | added |
---|
comment:4 by , 18 years ago
Milestone: | → 1.0 |
---|
This feature would also be a must for people (ab)using the TracReports for getting reports over changesets, before we could phase out the SQL reports.
The TracDev/Proposals/DataModel should make this possible.
We'll also have to think about whether queries should work on different types of objects. This could eventually lead to a merge of the Search module in the TracQuery module, as currently the Search module is performing unstructured search over different type of objects. See also #3375 for that.
Finally, the TicketQuery language should be generalized to make it possible to work on any kind of resource in the system.
comment:6 by , 14 years ago
Milestone: | triaging → next-major-0.1X |
---|---|
Severity: | normal → critical |
comment:7 by , 10 years ago
Owner: | removed |
---|
That's an interesting proposal.