It may be that we don't want to do this for the case given here, 'cause maybe people should always use Pointers for this sort of case, but there may be other user stories where this would be useful to have.
E.g. right now in tickets, the +status card has open, closed, documenting, etc. as plain text. Those cards have hard-coded searches to find the relevant cards. To automate that (as with tickets for item+*right+*structure), we could:
...add syntax/functionality to WQL to make it possible to reference a card's name, something like:
{"match": "_selfname"}
_leftname, _rightname
agree about the need. don't particularly like this solution.
What are some other ways to do it? Mm, allow inclusion in WQL:
{"match": "make card name referenceable in WQL+discussion"}
--John Abbe.....Wed Dec 03 14:01:41 -0800 2008
Write a user story instead?
--John Abbe.....Tue Jun 09 04:18:13 -0700 2009
make card name referenceable in WQL+discussed in support tickets
make card name referenceable in WQL+relevant user stories