`query` module is not supported

[haizaar@…]

If I use query module instead of report module, this plugin reports does not work.

[Russ Tyndall]

I assume you mean that the custom columns do not show up on the custom query page? If so, this is probably more of a trac bug than a bug with my plugin, though I will see if there is anything I can do to improve the functionality of this.

As stated on the user manual page, I tried to change trac as little as possible, so that this would be most likely to work in future versions of trac. In as much, I use trac custom fields to store the data. I also do not replace any of the default templates in trac, so hopefully if you have custom templates, this plugin should still function correctly. All of this is just to say, that if there is not an easy way to add new fields to the custom queries via some trac interface, I am unlikely to want to persue this further as part of this plugin.

Perhaps a new trac plugin to accomplish adding cutom fields to the query module would be a better approach. After looking into this further, I will leave some more notes here.

[haizaar@…]

No, that not what I've meant. Thanks for the verbatim answer, though. Here is the problem: setting

  [components]
  trac.ticket.report.* = disabled

in trac.ini (as stated at ​http://trac.edgewall.org/wiki/TracReports) - breaks all reports under Management page.

[Russ Tyndall]

Essentially, that is what you meant, even if you did not know it. Disabling the report handler causes the 'view ticket' button to default to the custom query view of tickets. Because management reports are handled automatically by the report handler, if you disable the report handler (which you are doing in that config line), trac doesn't know how to handle things at /report anymore.

Because the query handler, does not, to the best of my knowledge support trac custom fields yet, there is not a way to use the custom query handler for the Management reports.

Thankfully, having the reports enabled, does not in any way prevent you from using the custom query reports (albeit without the time fields).

Hope this helps, if you need anything further, please do not hesitate to ask,

Russ

[Russ Tyndall]

After poking about a bit, I have figured out how to add any one column to the query interface.

If you add order=columnname, that column name will be forced into the actual result set.

for example, to make total hours show on the custom query screen you can:

​https://trac.yoursite.com/TracEnv/query?order=totalhours

Hope this helps. If you want to poke about, or recompile your trac to fix this problem, you will want to look at ​http://trac.edgewall.org/browser/branches/0.10-stable/trac/ticket/query.py#L139

This also seems to be fixed, or at least different in Trac .11.

Either way the reports would not work there, however, the custom query page should supersede all of the functionality of the management page (other than maybe billing dates). Suffice it to say, that the management page should be somewhat different for Trac .11

Cheers,

Russ

[Russ Tyndall]

SEE #1653 - Is a ticket to wrap up all of the Trac .11 features

[haizaar@…]

Ok. Many thanks to your reply. To make it short: I'll stick with reports and wait for 0.11 :)

[haizaar@…]

Offtopic... Is there any way to disable billing facility?

[Russ Tyndall]

Um... do you just mean the set bill date stuff? It is not used internally, its only there to help keep trac of the time you bill, so if you do not use it, it will have no effect. As far as removing it, you would probably have to do this with javascript after the fact.

see #1621 and #1624