Will I be able to filter the queue according to areas in the future?
–Eriks
R. Eriks Goodwin, CEO
UniMatrix International Corporation
2101 East Main Street, Suite 900
Richmond, Virginia 23223-7050, U.S.A.
Tel: 804-780-0590 Fax: 804-780-0591
Computers * Web Sites * SDSL, T-1, T-3, DS-3
Will I be able to filter the queue according to areas in the future?
I’m not sure, but I think Jesse already has implemented this. Anyway, I’d
like to see Areas disappear some time in the future, when we have a
working keyword system.
Tobias Brox
aka TobiX
+47 22 925 871
nod There will be no areas in 2.0. In 2.x we’ll have a real keyword system,
which you will be able to filter the queue on.On Thu, May 04, 2000 at 09:55:29AM +0200, Tobias Brox wrote:
Will I be able to filter the queue according to areas in the future?
I’m not sure, but I think Jesse already has implemented this. Anyway, I’d
like to see Areas disappear some time in the future, when we have a
working keyword system.–
Tobias Brox
aka TobiX
+47 22 925 871
rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users
jesse reed vincent – jrvincent@wesleyan.edu – jesse@fsck.com
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
Transporters are so ungodly. if god had wanted us to travel great distances
instantaneously, he would have given us an internal
materialisation/dematerialisation control.
– Shoshe Cole
Quick question,
We are using areas to classify requests by client across different
queues, such that the EndUserSupport queue has areas ClientA and
ClientB, the AttackResponse queue has areas ClientA and ClientB, etc.
Will 2.0 support something similar? Or will we have to break queues
apart into, e.g., EndUser_A, AttackR_B, etc? (The latter seems to be
the conventional wisdom on this list…)
TIA
MJ Pomraning mjp@securepipe.com
SecurePipe Communications
2.0 will support something similar.On Wed, May 10, 2000 at 08:45:08AM -0500, Michael J. Pomraning wrote:
Quick question,
We are using areas to classify requests by client across different
queues, such that the EndUserSupport queue has areas ClientA and
ClientB, the AttackResponse queue has areas ClientA and ClientB, etc.Will 2.0 support something similar? Or will we have to break queues
apart into, e.g., EndUser_A, AttackR_B, etc? (The latter seems to be
the conventional wisdom on this list…)TIA
–
MJ Pomraning mjp@securepipe.com
SecurePipe CommunicationsFrom: Jesse <jesse@fsck.com>Subject: Re: [rt-users] Area sorting…
Date: Thu, 4 May 2000 11:11:09 -0400
To: Tobias Brox tobiasb@tobiasb.funcom.com
Cc: “R. Eriks Goodwin” egoodwin@unimatrix.com, RT List rt-users@lists.fsck.comnod There will be no areas in 2.0. In 2.x we’ll have a real keyword system,
which you will be able to filter the queue on.
jesse reed vincent – jrvincent@wesleyan.edu – jesse@fsck.com
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
that’s security the same way that asking for directions to topeka and
being told that a seal is a mammal is informative
-robin@apocalypse.org