On Aug 7, 8:30 pm, Ash <[email protected]> wrote:
> As per the suggestions from Trac, I disabled trac.ticket.report to try
> and use the newer trac.ticket.query plugin instead. (Report is
> deprecated and will go away eventually.)
You just need not to use it anymore, so do not spend time in writing
your own SQL reports, use the new Query Approach instead, that is what
the trac message means. If you disable the module, you will eventually
introduce new dysfunction in the system, because as of now it is not
yet completely isolated...

> I noticed that this left an empty 'Tickets' header in the left bar,
> but no links. Is there any way to get some back? (Besides re-enabling
> report module.)
Not really that list is actually a JavaScript loaded (partial) of the
report page. So you do not have to remove report, but replace the
report in SQL with the report as Custom Query. At the time the report
module is the only one that allows you to persist a query, and
disabling it is not a solution.

> Ideally, I'd love it if a wiki page could be inlined there, so we
> could create, for example, AgiloReports with a bullet list of
> TracQuery links there and have them populate the left bar.
You could think about making your own wiki pages with the report
inside, linked also as Custom Query, using the TicketQuery macro, than
the fact that those wiki will be the last changed will appear on top
of the Wiki list... that contains the last 10 pages modified.

> Anything like this possible?
Everything is possible... it is only a matter of time and costs ;-)

Best
ANdreaT

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH 
http://www.agile42.com and is focused in supporting Agilo for Scrum users.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/agilo?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to