Am Mittwoch, 2. Dezember 2015 06:14:03 UTC+1 schrieb RjOllos: > > > I agree it is a valuable feature, however we are really lacking > contributors these days and the few of us that are working on the projects > can't implement every nice-to-have feature in the limited time we have > available. I'd like to get more people involved in the project, but that is > difficult even someone commits to working some patches. Hopefully things > will pickup in the coming year. > > http://trac.edgewall.org/ticket/9617 >
Thanks for that ticket. I understand that new features require the resources to implement that. However I would give the custom query topic a high priority as Trac is a ticket system in the first place. And increasing number of tickets we encounter now that it's hard to maintain custom views on these tickets as known from the very early bugzilla and friends. The difference between reports and queries gets even more confusing if I change a custom query and save it, which leads to a "Edit Report" dialog and "Save Report" button, where I can review the SQL behind my custom query and save it. So behind the queries engine there is always a SQL report as well? What about if I like to re-arrange the queries? For now they have fixed index and inserting another custom query in the list is not possible easily, for example if I like to have the list sorted by project. Best regards. -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
