Use link under the View Tickets tab instead of Custom Query tab

[anonymous]

Adding yet another tab in the navigation bar can become problematic for any user having the TRAC_ADMIN permissions: the navigation bar becomes too long.

Wouldn't it be possible to use the same Custom Query link below the View Tickets link as in the default Trac behaviour ?

[anonymous]

It would be great if this ticket could be fixed, Im getting a way to long nav menu.

[Tonin]

The problem to the proposed behaviour is that the Custom Query link is taken care of inside the process_request method of the Trac ReportModule class (see trac/ticket/report.py code):

# Kludge: only show link to custom query if the query module is actually
# enabled
from trac.ticket.query import QueryModule
if req.perm.has_permission('TICKET_VIEW') and \
   self.env.is_component_enabled(QueryModule):
    req.hdf['report.query_href'] = req.href.query()

We see a direct test to the QueryModule to see if it's enabled.. However, the BatchModifyModule needs the QueryModule to be disabled to work. :(

To solve this problem, one should patch Trac, which is not so recommended, or make the BatchModifyModule behave like if it was the QueryModule which is enabled. Not sure how this last option is feasable. Anyone has a clue?

[Colin Guthrie]

This is solved in 0.11 via the use of a filter to adjust the output of the built in query page rather than actually create it's own one.

It would be pretty tricky to fix it properly for 0.10 without some kind of ugly hack or patch to Trac itself. So I think this can be closed...

If someone feels strongly to the contrary, please reopen.

[anonymous]

If someone feels strongly to the contrary, please reopen. ​rosetta stone french

[anonymous]

The problem to the proposed behaviour is that the Custom Query link is taken care of inside the process_request method of the Trac ReportModule class​rosetta stone french

[CuriousCurmudgeon]

This looks like it was reopened by a spam bot.