ticket,summary,type,release,owner,status,created,modified,_description,_reporter
13721,Wrong date in when plotting the stat using macro,defect,1.2,,new,2020-01-06T06:41:34+01:00,2020-01-06T07:04:07+01:00,"Tracticketstats 3.0.0dev
We started using it from 2020-01-01.
We have some 28 tickets created on that day.
I used the following macro to show stats in wiki page.
{{{
[[TicketStats(title = Total tickets 2020 Q1, height=250, daterange=2020-01-01;2020-04-01, res_days=1)]]
}}}

But it shows that 28 tickets were created on 2020-01-02.
All dates are one date advance. So,
 - 2020-01-01 stats are shown as 2020-01-02
 - 2020-01-02 stats are shown as 2020-01-03
 - 2020-01-04 stats are shown as 2020-01-04
and so on.",dewan.shamsul@…
3412,TracTicketStatsPlugin not showing any active tickets in the chart,defect,0.11,,new,2008-07-18T00:00:15+02:00,2016-09-06T05:05:50+02:00,"I installed TracTicketStatsPlugin for Trac 0.11. I have 2 active and 3 closed tickets. However, the chart says 0 tickets from 06/17/208 thru 07/17/2008. All the tickets are opened on 07/17/2008.

{{{
2008-07-17 22:35:42,546 Trac[main] DEBUG: Dispatching <Request ""GET u'/ticketstats'"">
2008-07-17 22:35:42,562 Trac[perm] WARNING: perm.permissions() is deprecated and is only present for HDF compatibility
2008-07-17 22:35:42,571 Trac[chrome] DEBUG: Prepare chrome data for request
2008-07-17 22:35:42,577 Trac[session] DEBUG: Retrieving session for ID u'firstname.lastname'
2008-07-17 22:35:42,616 Trac[main] DEBUG: 236 unreachable objects found.
}}}

Any ideas as to why I am not seeing the chart rendered with the right number of tickets plotted.
",anonymous
11165,TracStatsPlugin does not properly count imported tickets,defect,1.0,,new,2013-06-14T06:11:05+02:00,2016-09-06T05:05:50+02:00,"Change [13107] changed the results of the get_num_closed_tix() and get_num_open_tix() queries.  The new version does not cooperate with batch-modified tickets.  Neither version completely cooperates with tickets imported with status=closed via the TicketImport plugin.

Reproduction steps:
 1. Use TicketImport to import a set of bugs from CSV, some with open status and some with closed.
 1. Version [13106] of these methods do not correctly add the already-closed tickets to the new and closed statistics; there also appears to be a miscount.  Version [13107] of these methods count the already-closed tickets as still-open.

Attempted failed workaround: Taking all the closed tickets, re-opening and re-closing them still does not get TicketStats to correctly count them.

Note: I am not sure it is entirely possible to get accurate statistics just by looking at the ticket_change table.  The [13106] version of these queries look like they'll provide more accurate results.  I believe it is far more important to users for these statistics to be accurate rather than fast.",achittur@…
8703,SQL injection vulnerability/SQL compatibility,defect,0.11,Ryan J Ollos,reopened,2011-04-14T01:49:55+02:00,2017-07-11T06:05:59+02:00,"The arguments to the SQL statements are not properly escaped.  This results in a possibility of SQL injection, and also database compatibility issues.

Disclaimer - I'm not really python programmer so the attached patch may not be the optimal approach.  However it does remove the % operator which is at the root of the SQL injection problem, and also removes the double quotes around the milestone value (which doesn't work with postgres 9.x).",anonymous
10073,Selecting tickets by component or owner,enhancement,0.11,,new,2012-06-08T08:00:03+02:00,2016-09-06T05:05:50+02:00,It would be great if it is possible to select stats also by component or owner. Just like it's done selecting by milestone.,barthing@…
8330,Plugin has stop workin',defect,0.12,,new,2010-12-21T16:25:30+01:00,2016-09-06T05:05:50+02:00,"I've installed plugin and all works, but since 2 days it doesn't draw anymore the stats.

On log is nothing to appreciate. (trac.log in DEBUG mode) and here is the output from the bottom of the statssite:

{{{
Logger Console

INFO1649638ms (+0) 15:41:53:

Connection

Connection object for transaction 5 destroyed.

INFO1649638ms (+776) 15:41:53:

Connection

Success callback with scope. HTTP code is 200

INFO1648862ms (+0) 15:41:52:

Connection

Transaction 5 sent.

INFO1648862ms (+1) 15:41:52:

Connection

Default HTTP header X-Requested-With set with value of XMLHttpRequest

INFO1648861ms (+7565) 15:41:52:

Connection

XHR object created for transaction 5

INFO1641296ms (+0) 15:41:45:

Connection

Connection object for transaction 4 destroyed.

INFO1641296ms (+1647) 15:41:45:

Connection

Success callback with scope. HTTP code is 200

INFO1639649ms (+1) 15:41:43:

Connection

Transaction 4 sent.

INFO1639648ms (+1) 15:41:43:

Connection

Default HTTP header X-Requested-With set with value of XMLHttpRequest

INFO1639647ms (+1624535) 15:41:43:

Connection

XHR object created for transaction 4

INFO15112ms (+1) 15:14:38:

Connection

Connection object for transaction 3 destroyed.

INFO15111ms (+1199) 15:14:38:

Connection

Success callback with scope. HTTP code is 200

INFO13912ms (+0) 15:14:37:

Connection

Transaction 3 sent.

INFO13912ms (+2) 15:14:37:

Connection

Default HTTP header X-Requested-With set with value of XMLHttpRequest

INFO13910ms (+2355) 15:14:37:

Connection

XHR object created for transaction 3

INFO11555ms (+0) 15:14:35:

Connection

Connection object for transaction 2 destroyed.

INFO11555ms (+255) 15:14:35:

Connection

Success callback with scope. HTTP code is 200

INFO11300ms (+0) 15:14:35:

Connection

Transaction 2 sent.

INFO11300ms (+1) 15:14:35:

Connection

Default HTTP header X-Requested-With set with value of XMLHttpRequest

INFO11299ms (+3927) 15:14:35:

Connection

XHR object created for transaction 2

INFO7372ms (+0) 15:14:31:

Connection

Connection object for transaction 1 destroyed.

INFO7372ms (+256) 15:14:31:

Connection

Success callback with scope. HTTP code is 200

INFO7116ms (+1) 15:14:30:

Connection

Transaction 1 sent.

INFO7115ms (+1) 15:14:30:

Connection

Default HTTP header X-Requested-With set with value of XMLHttpRequest

INFO7114ms (+6653) 15:14:30:

Connection

XHR object created for transaction 1

INFO461ms (+1) 15:14:24:

Connection

Connection object for transaction 0 destroyed.

INFO460ms (+322) 15:14:24:

Connection

Success callback with scope. HTTP code is 200

INFO138ms (+0) 15:14:23:

Connection

Transaction 0 sent.

INFO138ms (+0) 15:14:23:

Connection

Default HTTP header X-Requested-With set with value of XMLHttpRequest

INFO138ms (+1) 15:14:23:

Connection

Initialize transaction header X-Request-Header to XMLHttpRequest.

INFO137ms (+75) 15:14:23:

Connection

XHR object created for transaction 0

INFO62ms (+62) 15:14:23:

LogReader instance0

LogReader initialized

INFO0ms (+0) 15:14:23:

global

Logger initialized
}}}

Attached the capture of the plugin
",T. N.R
7001,Optimize SQL queries,enhancement,0.11,,new,2010-04-17T23:03:08+02:00,2016-09-06T05:05:50+02:00,"The plugin is very useful. Thanks a bunch for that.

I've noticed the plugin queries database twice for the same dataset. Also the queries return large number of data elements. These slow down significantly in a system with lots of tickets.

Attached here is my modified ticketstat.py to speed things up. It only queries the dataset onc with and smaller dataset using SQL filer.
",austin
6202,More parameters to the charting backend - Use different Chart Types from Default,enhancement,0.11,,new,2009-11-13T13:53:43+01:00,2016-09-06T05:05:50+02:00,"Is it possible to pass on a parameter to the charting backend to display different chart types e.g. Pie, Line, Stacked Bar etc.
Is it also possible to change the width of the chart.",Bill Meyer
5878,Erroneous stats when using custom status/workflow counted twice in Open tickets formulae,defect,0.12,,new,2009-09-25T16:33:50+02:00,2016-09-06T05:05:50+02:00,"Here, we use a custom workflow which has a ""testing"" status.  See TestingWorkflow.  All tickets with that status seem to be counted twice in the resulting ""Open tickets"" count.

The queries should also count unknown statuses, or should consider that any bug that status <> 'closed' is an open bug.

We cannot use the plugin since it gives erroneous stats in our use case. :(",samuelp@…
7868,Detailed statistics view,enhancement,0.12,,new,2010-10-21T04:00:39+02:00,2016-09-06T05:05:50+02:00,"Current statistics view can only base on all tickets. Is it possible to show/generate statistics by ticket owner/reporter, assigned by user. That will be more accurate information, thanks.",anonymous
7541,A warning should be displayed when the Start and End date are invalid,enhancement,0.11,,new,2010-08-23T08:15:07+02:00,2016-09-06T05:05:50+02:00,"When the start date and/or end date are not entered, an error is thrown, but this error is only visible in the log file and not to the client. A message should be presented to the user so that they can take corrective action. Furthermore, we should check for start_date > end_date, and other reasonable invalid entries.

I attempted to implement this using the add_warning function in trac.web.chrome, but since the entire page is not updated when Update is pressed, this seems to be more difficult to accomplish than I initially thought.
",Ryan J Ollos