On 29/05/13 03:15, Pranay B. wrote:
Hello Everyone- Good news! My proposal for 'customizable
time series reports' has been accepted to GSoC 2013.
This confers upon me the need to further understand the
community developments and its corresponding nuances
as I continue to internalize the developments thus far.
As I understand it, the 'ticket_changes' table keeps track
of changes. I am especially interested in how the
'field' value (in text) has been used in the past for creating reports.
Thank you,
Pranay B.
Hi Pranay,
Great to hear from you!
So, if I remember correctly the ticket_change table will list all the
changes, indexed by ticket, time and field. The field can be pretty much
any db field that is available to be set on a ticket and can also be a
comment field.
Most reports do not make use of this field as for the most part there is
a focus on the current state. The only report that I know of that does
reference this table is https://issues.apache.org/bloodhound/report/7
which is only checking whether an author of any change associated with a
ticket is the same as the user running the query.
I have not checked particularly carefully whether custom queries make
use of the ticket_change table but there probably is not too much extra
interesting happening there.
If you are interested in report 7, you should be able to find it
described in python in trunk/trac/trac/db_default.py (lines 296 to 331).
The timeline is the feature that makes particular use of the
ticket_change table as it is intended to display such changes which
might be of more interest.
Cheers,
Gary
