Error Billing Reports

[anonymous]

getting the following error when clicking on any of the Billing Reports on the Management page:

Report execution failed: ORDER BY column number 0 out of range - should be between 1 and 7

Using

Trac: 0.11rc1 Python: 2.5.2 (r252:60911, Apr 21 2008, 11:29:43) [GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)] setuptools: 0.6c8 SQLite: 3.4.2 pysqlite: 2.4.0 Genshi: 0.5dev-r851 mod_python: 3.3.1 jQuery: 1.2.3

Any ideas?

Thanks!

[Russ Tyndall]

I am not sure having never seen that error, but try editing the report and changing the order by statement in the Ticket Work Summary report from:

ORDER BY __ticket__, _ord ASC, time ASC

to

ORDER BY __group__, _ord ASC, time ASC

and let me know if that fixes it. There may have been a change in how column aliasing is resolved in the order by (but I would sor of doubt it). If it doesnt work, just change it back so that this will not be the source of future errors.

[anonymous]

Replying to bobbysmith007:

Thanks for the fast reply! But unfortunately that didn't help me. I tried the suggested changes to the report (of course with a backup copy), still the same error message. Also skipping the ORDER BY clause didn't change anything. I use custom workflows and other plugins in my trac project so I set up a new and clean trac project to rule out that the error comes from my own workflows and other plugins. But the error is the same there.

[Russ Tyndall]

It still gives you an error about the order-by column even when the order by clause is entirely removed! That is strange indeed.

I replicated the error on my end by upgrading trac, genshi and tande to the head revisions. Trying to figure it out now

[Russ Tyndall]

I finally tracked down what was going on. It seems the group column that trac reports use to group the results is broken in the trac head at the moment.

This is a bug in Trac11rc1 see: ​http://trac.edgewall.org/ticket/7179

Hopefully it will be fixed soon. There is a patch for this on the ticket if you are the adventurous type.

Thanks for the good bug report and excellent feedback,

Russ

[Russ Tyndall]

This seems to be fixed in the head of ​http://svn.edgewall.com/repos/trac/branches/0.11-stable/