[Rtir] Handling different clients with queues
colintempler at gmail.com
Fri Feb 3 12:58:15 EST 2012
On Wed, Feb 1, 2012 at 6:52 PM, Ruslan Zakirov <ruz at bestpractical.com> wrote:
> On Wed, Feb 1, 2012 at 21:44, Colin <colintempler at gmail.com> wrote:
>> Reading through lib/RT/IR/Constituencies.pod, the correct procedure would be:
>> - create a new Incident queue for each client
>> - create a new constituency for each queue
>> - create a new group and users for each queue
>> Is that correct?
> Not sure, it's been a while since I touched that part.
Ok, I now have tested this. Here's the output instead of writing down:
# perl add_constituency --name CLIENT1
defined(%hash) is deprecated at
(Maybe you should just omit the defined()?)
Check that the constituency exists
If you continue then we'll...
* add new constituency value: 'CLIENT1'.
* create queue 'Incidents - CLIENT1' if it doesn't exist
* create queue 'Incident Reports - CLIENT1' if it doesn't exist
* create queue 'Investigations - CLIENT1' if it doesn't exist
* create queue 'Blocks - CLIENT1' if it doesn't exist
* create group 'DutyTeam CLIENT1' if it don't exist
* create group 'ReadOnly CLIENT1' if it don't exist
* grant basic set of rights to the groups on the queues
I have done some tests and the only thing I see missing for my
workflow is a different CustomField, the same as Constituency. In this
case a "Constituency - CLIENT1" would be created as well.
Now the reason behind this is as I'm opening a ticket for CLIENT1, no
other Constituency should be visible.
Right now with only one CustomField Constituency where all
constituency are put, all clients have access to them and can select
them on a new ticket.
What do you think?
More information about the Rtir