Steffen, Thanks, I continued experimenting and when I moved the keywords field before the format field, it worked fine. Must be the order in which it the macro processes these expressions. I incidentally did change to ~= after reading over the doc; I actually had done that before writing my question, but really appreciate the fast response.
Thanks! Paul ---------------------------- Paul Boos OPP/ITRMD/SDDB [email protected] O: 703-305-0759 M: 703-307-4322 Twitter: @paul_boos LinkedIn: http://www.linkedin.com/in/paulboos Blog: http://boosianspace.posterous.com/ Author of the Project Leadership Manifesto: http://projectleadermanifesto.posterous.com/ “Most people do not listen with the intent to understand; they listen with the intent to reply.” - Stephen Covey "Treating people like resources to be planned, organized, and mined, and then expecting passionate commitment is insane." - Tony DaSilva "Strict control is something that matters a lot on relatively useless projects and much less on useful projects where value is the measure." -Tom DeMarco, IEEE Software "Follow not in the footsteps of the masters, but rather seek what they sought." - Stephen Covey From: Steffen Hoffmann <[email protected]> To: [email protected] Date: 07/24/2012 01:42 PM Subject: Re: [Trac] Keywords Query Sent by: [email protected] -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 24.07.2012 16:48, wrote Paul Boos: > I have a field called Keywords (via the keywords plugin); this contains > a list of keywords (duh!). Everyone has a 'keywords' field in tickets, because it's a standard one, unrelated to any Trac plugin. You speak about that, don't you? > I'm setting up a specific report using TracQuery inside a wiki page. > When I use keywords=accreditation (the keyword of interest), I get no > returns. TracWiki provides a good, embedded documentation for you. As you see there [1], TracQuery is a synonym for ticket query. There is the (custom) query module as well as the wiki macro TicketQuery. I guess, this is what you're speaking about here. By writing [[TicketQuery(keywords~=kw1|kw2|kw3)]] you call a specific query over (all) tickets, that contain (any of) the specified keywords. To match keywords within possibly multiple keywords for a ticket you need "contains": "~=" instead of "is equal to": "=". > If I swap this out with keywords~=accreditation, when format=count I get > the proper count back, but if I leave that out to actually get a list of > tickets, I have no results. Leaving out only the 'format' argument you should get the list instead of the row count. > What am I missing? Quotes? Double quotes? Something else? Take a look at the query syntax, please. Quotes are only needed to mask white-space. Dunno, what could go wrong there for you. Maybe you missed to tell us something else that is relevant for this issue. Steffen Hoffmann [1] http://trac.edgewall.org/wiki/TracQuery [2] http://trac.edgewall.org/wiki/TracQuery#QueryLanguage -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAO3pIACgkQ31DJeiZFuHfxcgCglihJRZCfoV46268ePrWq6phJ MSgAoOATjh7D5PA1nScLZx0hs20YMoJS =M3Eb -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to trac-users [email protected]. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Trac Users" 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/trac-users?hl=en.
<<inline: graycol.gif>>
