Re: [Trac] Trac 1.0.1 custom field question [SOLVED]

2013-12-05 Thread Roger . Oberholtzer
Indeed, the empty string was the problem. This does what I expected: [[TicketQuery(sprintinfo!=)]] Even if it looks incorrect to my programmer's eye... -- Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholt.

Re: [Trac] Trac 1.0.1 custom field question

2013-12-04 Thread Ethan Jucovy
On Wed, Dec 4, 2013 at 5:42 PM, RjOllos wrote: > On Wednesday, December 4, 2013 8:58:54 AM UTC-8, Ethan Jucovy wrote: > >> I then edit a ticket so that the sprintinfo field exists for a ticket. I >>> then >>> do a query, hoping to see tickets for which sprintinfo has a value: >>> >>> [[Ti

Re: [Trac] Trac 1.0.1 custom field question

2013-12-04 Thread RjOllos
On Wednesday, December 4, 2013 8:58:54 AM UTC-8, Ethan Jucovy wrote: > I then edit a ticket so that the sprintinfo field exists for a ticket. I >> then >> do a query, hoping to see tickets for which sprintinfo has a value: >> >> [[TicketQuery(sprintinfo!="")]] >> > > The following spellin

Re: [Trac] Trac 1.0.1 custom field question

2013-12-04 Thread Ethan Jucovy
> > I then edit a ticket so that the sprintinfo field exists for a ticket. I > then > do a query, hoping to see tickets for which sprintinfo has a value: > > [[TicketQuery(sprintinfo!="")]] > The following spelling works for me: [[TicketQuery(sprintinfo=!)]] That is, exclamation point af

[Trac] Trac 1.0.1 custom field question

2013-12-04 Thread Roger . Oberholtzer
I have added a custom field to a ticket, like this: sprintinfo = textarea sprintinfo.cols = 80 sprintinfo.format = wiki sprintinfo.label = Sprint information sprintinfo.order = 5 sprintinfo.rows = 10 sprintinfo.value = I then edit a ticket s