Opened 18 years ago
Last modified 10 years ago
#6145 new enhancement
Query correlation with SVN commits
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | low | Milestone: | next-major-releases |
| Component: | general | Version: | 0.10-stable |
| Severity: | normal | Keywords: | xref |
| Cc: | DStrickler@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
The one thing that we keep looking to report on, that I can not find an easy way to do, is show tickets that where closed between SVN rev X and SVN rev Y.
As far as I can tell there is no way to access the SVN information (log, rev, etc…) to cross correlate it with the ticket data.
Note there are many reports that I used the SQL report facility for that I can not do in the query module. If you guys drop the SQL reports the Query module needs some significant improvements.
I will try to create a more detailed ticket about the reporting system, in general, later; right now this ticket is just to address data cross correlation with SVN data.
Thanks! Trac is very nice!
Note, I am the Sr. Project Manager for Rosetta Stone's software development group. We have about 7-8 teams all using Trac.
Attachments (0)
Change History (4)
comment:1 by , 18 years ago
| Keywords: | xref added |
|---|---|
| Milestone: | → 1.0 |
comment:3 by , 15 years ago
| Milestone: | triaging → next-major-0.1X |
|---|---|
| Priority: | normal → low |
| Severity: | major → normal |
The ability to form a query telling which tickets have been closed in a given revision range would be very useful, indeed.
Assuming we have a revision range (e.g. from the log view), we would then have to get for each revision the corresponding ticket(s) that were closed at this occasion (#508). The results could then be "piped" through the report module (#533).
comment:4 by , 10 years ago
| Owner: | removed |
|---|
See also googlegroups:trac-users:4d9614c3348e59de