Don't do that. Another reason why customer based queues are a bad idea. Tickets don't know what groups they're a member of. Groups don't know what tickets belong to them.
You'll need to redo the security model of the tickets to accomplish your goal. On Fri, Sep 7, 2012 at 3:53 PM, Leonardo Certuche < [email protected]> wrote: > Hello again, > > I just checked what Gerald advised, the documentation on that parameter > reads: > > Defines the groups every customer user will be in (if CustomerGroupSupport >> is enabled and you don't want to manage every user for these groups). >> > > The thing is that they DO want to have separate groups for different > customers, they'll split customers in groups so bad, that what they're > expecting is being able to use the CompanyTickets button in order to let > each customer see ALL tickets on queues associated to the group the > customer has permission on. Any ideas? > > Thanks! > > Leonardo Certuche > > > > On 7 September 2012 14:32, Leonardo Certuche < > [email protected]> wrote: > >> Hello Gerald! >> >> Thanks for your answer! I'm going to try with CustomerGroupsAlwaysGroups >> to see if it does what the customer expects. >> >> Regards, >> >> Leonardo Certuche >> ITSM Consultant / COO >> (57) 301 284 6250 >> (57) 4 320 7960 ext 1002 >> www.itconsultores.com.co >> Cra 41 Nro 9 - 51 Edificio Arteria Of 104 >> Medellín, Colombia >> >> >> >> On 7 September 2012 13:03, Gerald Young <[email protected]> wrote: >> >>> Besides which, "CustomerGroupsAlwaysGroups" = users means that this >>> customer could be able to see all tickets. >>> >>> >>> On Fri, Sep 7, 2012 at 2:01 PM, Gerald Young <[email protected]> wrote: >>> >>>> Hello, Leonardo! >>>> >>>> This doesn't sound like a healthy thing to do, unless you *promise* >>>> that other customers won't be in that customer group. >>>> >>>> On Fri, Sep 7, 2012 at 12:38 PM, Leonardo Certuche < >>>> [email protected]> wrote: >>>> >>>>> Hello there, >>>>> >>>>> One of our customers wants to change the behaviour of the >>>>> CompanyTickets button on the customer interface. Instead of showing the >>>>> tickets associated with the CustomerID of the Customer, they want to show >>>>> there the tickets that are in the groups where the customer has >>>>> permissions >>>>> to (we already have CustomerGroupSupport enabled). >>>>> >>>>> We where checking the code at Kernel/Modules/CustomerTicketOverview.pm >>>>> and it seems to refer to the following lines: >>>>> >>>>> CompanyTickets => { >>>>> All => { >>>>> Name => 'All', >>>>> Prio => 1000, >>>>> Search => { >>>>> CustomerID => >>>>> [ $Self->{CustomerUserObject}->CustomerIDs( >>>>> User => $Self->{UserLogin} ) ], >>>>> OrderBy => $Self->{OrderBy}, >>>>> SortBy => $Self->{SortBy}, >>>>> CustomerUserID => $Self->{UserID}, >>>>> Permission => 'ro', >>>>> }, >>>>> }, >>>>> >>>>> Is there any way we can change the criteria to match this customer's >>>>> expectation? >>>>> >>>>> Thanks, >>>>> >>>>> Leonardo Certuche >>>>> www.itconsultores.com.co >>>>> Medellín, Colombia >>>>> >>>>> --------------------------------------------------------------------- >>>>> OTRS mailing list: otrs - Webpage: http://otrs.org/ >>>>> Archive: http://lists.otrs.org/pipermail/otrs >>>>> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs >>>>> >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> OTRS mailing list: otrs - Webpage: http://otrs.org/ >>> Archive: http://lists.otrs.org/pipermail/otrs >>> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs >>> >> >> > > --------------------------------------------------------------------- > OTRS mailing list: otrs - Webpage: http://otrs.org/ > Archive: http://lists.otrs.org/pipermail/otrs > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs >
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
