On Mon, Nov 3, 2008 at 1:55 PM, Christopher Arndt <[EMAIL PROTECTED]> wrote:
>
> Lukasz Szybalski schrieb:
>> On Mon, Nov 3, 2008 at 8:55 AM, Christopher Arndt <[EMAIL PROTECTED]> wrote:
>>> Lukasz Szybalski wrote:
>>>> Hello,
>>>> Is there a reason the "view tickets" screen asks me to do a custom
>>>> query instead of showing the usual choices aka. Reports.
>>>>
>>>> I'm trying to view all tickets and I can't seem to find how to do it.
>>> I changed the page to which "View Tickets" points to use the query
>>> module instead of the report module. You can see all tickets, if you
>>> just remove the option to search only for your own tickets at the top of
>>> the page. If you are not logged in, you'll see all open tickets by default.
>>>
>>> BTW, under the new header link "Ticket queries" there are are links to a
>>> couple of canned queries. I you have any suggestions for additional
>>> queries to add to this page, I'll add them.
>>>
>>
>> I'm more used to something like this:
>>
>> http://trac.edgewall.org/report
>>
>> I usually go through report#1, then #5  to look at some bugs that are
>> out there for all versions to see if I'm not duplicating anything.
>
> I like the query interface better, but I have now re-enabled the report
> interface and it is available under the "View Tickets" header link again
> (I didn't find a way to link it form a different header label).
>
> Is this ok for everybody?
>
sorry for jumping late, but I actually disagree not only the reports
module is deprecated, it performs badly, the correct way of doing this
if you want a "report" is to use the TicketQuery macro. I personally
do as Chris suggests.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears Trunk" group.
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/turbogears-trunk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to