Internal Error on Tickets Pane (no such column: ticket)

[kofalt]

Installed plugin on Trac 0.11 and works fine except for tickets link, which gives an internal error: OperationalError: no such column: ticket

Trace: File "C:\Python25\Lib\site-packages\Trac-0.11.5-py2.5-win32.egg\trac\web\main.py", line 444, in _dispatch_request dispatcher.dispatch(req) File "C:\Python25\Lib\site-packages\Trac-0.11.5-py2.5-win32.egg\trac\web\main.py", line 205, in dispatch resp = chosen_handler.process_request(req) File "build\bdist.win32\egg\tracstats\web_ui.py", line 113, in process_requestFile "build\bdist.win32\egg\tracstats\web_ui.py", line 822, in _process_ticketsFile "C:\Python25\Lib\site-packages\Trac-0.11.5-py2.5-win32.egg\trac\db\util.py", line 60, in execute return self.cursor.execute(sql) File "C:\Python25\Lib\site-packages\Trac-0.11.5-py2.5-win32.egg\trac\db\sqlite_backend.py", line 58, in execute args or []) File "C:\Python25\Lib\site-packages\Trac-0.11.5-py2.5-win32.egg\trac\db\sqlite_backend.py", line 50, in _rollback_on_error return function(self, _args, *_kwargs)

System Information: User Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 Trac: 0.11.5 Python: 2.5.4 (r254:67916, Dec 23 2008, 15:10:54) [MSC v.1310 32 bit (Intel)] setuptools: 0.6c9 SQLite: 3.3.4 pysqlite: 2.3.2 Genshi: 0.6dev-r0 mod_python: 3.3.1 Pygments: 1.2.2 Subversion: 1.6.4 (r38063) jQuery: 1.4.2

We do use a custom field for our ticket (a radio option), but otherwise it is a very vanilla install.

[mrjbq7]

Could you try again? I modified the SQL used in a way that might avoid a naming problem with the "ticket" column.

[kofalt]

Err, I don't know how to update a Trac plugin. Do I just download the source again and make another call to easy_install?

[mrjbq7]

I typically use "python setup.py install", rather than easy_install, but that's the idea, yes.

[kofalt]

Downloaded latest source, ran "python setup.py install", restarted webserver. Tickets view now works (is there supposed to be a red line at the bottom of the graph generated?). I also think I know why the Code view is failing, which I will post in the other issue I created (#2).

[mrjbq7]

I added labels to the ticket graph. Right now it shows number of opened (blue) and number of assigned (red). The ticket and wiki pages are less mature than the code pages, and I'd love feedback to improve them.

[kofalt]

I think the assigned tickets line may be broken, since it shows always 0 even through there are definitely accepted tickets. This is an experimental server, so there are quite a few "new" tickets, but doing a quick search at least half of the tickets in an active state are accepted by some user or another. Image link: http://imgur.com/D9zW8.jpg

Let me know if you want this in a separate issue.

[kofalt]

For initial feedback, I would be happy to assist you in maturing this plugin, as it seems like quite a cool project. My initial reaction: 1) For some of the longer content, it would be nice to have a mutli-column layout (graphs to the right of top stats table, for example) rather than being pages long. 2) I wish I could call some of these in macros, for example use [WikiLatestChanged(3)] to show the latest 3 wiki edits, or [[CommitsByMonth]] to render the commits-by-month graph on the Wiki home page.

[mrjbq7]

I think it is not tracking assigned properly, I switched it to accepted, does that work better?

[mrjbq7]

Btw, thanks for the feedback!

[kofalt]

The graph now works properly with your latest changes. I will open an issue with more extensive feedback/requests later.