iki syntax that
had been used wasn't getting parsed properly, but I couldn't find a
reference for the new syntax, even in the svn source for Wifty. I ended
up inferring enough syntax that I could make a usable page, but it was
harder than it had to be.
--
Aaron D. Ball <[EMAI
DependsOn = 'NULL'
and
DependsOn != 'NULL'
do what I want in that respect. I can't say I have a terribly good
sense of the syntax of TicketSQL at this point, though.
Any suggestions for how to find tickets whose dependencies, if any, are
all closed? Is there a
s" (tickets with no new/open
dependencies) and top-level projects (tickets with dependencies and that
nothing depends on).
--
Aaron D. Ball <[EMAIL PROTECTED]>
Senior Systems Analyst
Broad Institute of MIT and Harvard
___
http://lists.bestp
As Stephen said: the UI is a significant improvement aesthetically.
A few suggestions:
* Text size shouldn't vary between columns with similar contents.
Actually, this seems to be a bug: the id column in "10 highest priority
tickets I own" is actually showing Status.
* There is some optical
the
wiki or the book.
--
Aaron D. Ball <[EMAIL PROTECTED]>
Senior Systems Analyst
Broad Institute of MIT and Harvard
___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: [
RT folks,
I've got a number of saved-query boxes on my RT home page to keep track
of various classes of tickets I own or am watching. I'd like to make
them available to my co-workers without having to rewrite the query for
each user.
Is there a way to create a query that refers to the current
