[rt-users] What criteria do you use when deciding the number of instances of RT?

[Todd Chapman]

I have had to think about this a lot. Maintaining one RT with customizations
for lots of different groups can be challenging. Maintaining multiple RT
instances and trying to keep some customizations in sync across those
instances can also be a bit of a pain.

So what it comes down to for me is risk. I can't have my externally facing
customer service queues being screwed up by customization for my internal
queues. So for me customer service gets its own instance and everyone else
gets another instance.

-Todd

On 1/9/08, james machado <hvgeekwtrvl at gmail.com> wrote:
>
> Hi All,
>
> My question is both hypothetical and practical.  I've got RT deployed in
> my I.T. department doing what it does best and it's working well.  I've
> put feelers out to some other departments that I think could benefit from RT
> to see if they would be interested in having it setup for them.  I am finely
> getting some positive responses so I'm looking for some guidance on
> deployment options.  I am trying to decide if I should share an instance of
> RT among 1+ departments or create a new instance of RT for each department.
> Hardware is not an issue either way, nor does it look like the traffic
> volume will be an issue.  These are all internally created tickets with no
> Internet access to my RT instance.  If Internet access were required then a
> separate instance of RT would be desirable.
>
> So what I am looking for from people who have either had this issue or
> thought about it is: what factors you would take into account when deciding
> on 1 or more instances of RT and why.
>
> Thanks,
>
> James
>
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
>
>
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> Buy a copy at http://rtbook.bestpractical.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20080110/de1535c9/attachment.htm>