often we end up duplicating search components. For example, many of our ticket searches discard closed tickets, which takes a lot of words and makes the system more fragile. We want to be able to reuse common search elements.
"found_by":CARD_DEF should take the card_def from the search card (or cards) specified.
I think almost all of the searches on Tickets and Tickets by kind repeat the closed status stuff.
Related support tickets:Relevant user stories:add one
no idea what should happen if the CARD DEF returns multiple cards. I'm content not to support that just yet.
Were you thinking of CARD DEF as something in {}s? (and thus able to return more than one card?) How about just making it simply the name of a card?
--John Abbe.....Mon Mar 09 22:41:45 -0700 2009
If you're talking about what the whole thing returns, i thought the point was that that it could return more than one card (eg all the Tickets that aren't closed). Probably i'm missing something obvious here...
--John Abbe.....Mon Mar 09 22:43:49 -0700 2009
a card name is the simplest form of card def. so, yes, the simple case would be something like:
"returned_by":"Closed Cards"
where Closed Cards is a card name. The multiple card thing I was talking about is that you could do something like
"returned_by":{"type":"Search","edited_by":"John Abbe"}
which would give you all of the cards returned by any search card John Abbe had edited. I don't know of a good use case right now, and it could be hard (or not?), but it would be consistent with how WQL generally works.
--Ethan McCutchen.....Wed Mar 18 14:31:44 -0700 2009
As I was implementing I realized found_by would be a little shorter and a tad less geeky. For now I just implemented the simple form.
--Ethan McCutchen.....Thu Mar 19 12:09:50 -0700 2009
(I think we'd need more of evidence of need before we decided to implement the multi thing.)
--Ethan McCutchen.....Thu Mar 19 12:10:45 -0700 2009
actually, I figured out the need. Daisy chaining, as in being able to refer to _left in found_by. So the multiple thing is now implemented, too.
--Ethan McCutchen.....Thu Mar 19 12:54:23 -0700 2009
testing on http://sandwagn.wagn.org/wagn/WQL_testing - definitely at least some breakage (late for cooking dinner...)
--John Abbe.....Thu Apr 16 17:16:41 -0700 2009
_self in WQL refers to the card on the left. If you refer to _left in Sort By name+*rform, then in "User+*type_cards+sort by name", self= 'U+*t', left=User, and right="*type cards". Since User is not a search card, it breaks.
--Ethan McCutchen.....Thu Apr 16 21:10:02 -0700 2009
Almost ready to close. Wanted to test what Ethan referred to as, "Daisy chaining, as in being able to refer to _left in found_by." but not getting it. Say more?
--John Abbe.....Thu Apr 23 16:32:08 -0700 2009
I just meant the kind of thing we wanted to do with "by update" or "by name". chaining bits of WQL together via plus cards.
--Ethan McCutchen.....Fri Apr 24 12:02:49 -0700 2009
(in the WQL itself it will usually be _self, not _left)
--Ethan McCutchen.....Fri Apr 24 12:03:37 -0700 2009
phew. was worried you were talking about a whole 'nother category of thing.
--John Abbe.....Fri Apr 24 16:07:08 -0700 2009
Note that when you use found_by, you lose the order, so reverse order+*right+*content doesn't do what you might want it to.
--John Abbe.....Mon Apr 27 23:51:52 -0700 2009
Notes
