On 05/01/17 11:12 AM, Matt Zagrabelny wrote:
...and I see that Shawn has answered, too. Here is what I had to say:
"stalled" is an active status. I know the word feels "inactive", but
according to the default lifecycle, it is active.
https://github.com/bestpractical/rt/blob/stable/etc/RT_Config
Okay, I can see that. I was thinking of active/inactive as now, as in a
stalled ticket is inactive until someone un-stalls it. But from RT's
perspective, it does make sense that a ticket not deleted or resolved is
still, in some way, active. I'll have to adjust my crontool script too, or
people wil
...and I see that Shawn has answered, too. Here is what I had to say:
"stalled" is an active status. I know the word feels "inactive", but
according to the default lifecycle, it is active.
https://github.com/bestpractical/rt/blob/stable/etc/RT_Config.pm.in#L3034
On Thu, Jan 5, 2017 at 10:07 AM,
> On Jan 5, 2017, at 10:56, Alex Hall wrote:
>
> Hey all,
Hi Alex,
> I just did a search:
> Priority > 9 and Status = '__active__'
> Five of the resulting tickets are stalled, but I thought __active__ ignored
> stalled tickets. Any idea why they're appearing? Did I miss a setting or
> someth
On Thu, Jan 5, 2017 at 11:01 AM, Matt Zagrabelny wrote:
> __Active__ is case sensitive, I believe.
>
I should have said that I tried capital and lowercase A in my searches,
along with making the word all caps. I keep getting the same result.
> -m
>
> On Thu, Jan 5, 2017 at 9:56 AM, Alex Hall
__Active__ is case sensitive, I believe.
-m
On Thu, Jan 5, 2017 at 9:56 AM, Alex Hall wrote:
> Hey all,
> I just did a search:
> Priority > 9 and Status = '__active__'
> Five of the resulting tickets are stalled, but I thought __active__ ignored
> stalled tickets. Any idea why they're appearing?
