[rt-users] rt 4.0.5 - Autocomplete field type for external custom field does not work for non root user

[Ruslan Zakirov]

Hi,

You need fixes from 4.0/context-on-custom-fields branch.

On Tue, Feb 28, 2012 at 20:32, Jim Lesinski <jim.lesinski at gmail.com> wrote:
> I turned on debug (*new to me) and it looks like this is the relevant error
> in the logs:
>
> Feb 28 11:22:11 buf-rtdev RT: Permission denied. User #63 has no
> SeeCustomField right on CF #13
>
> If I assign SeeCustomField directly to the custom field (#13) for RTUser,
> then the autocomplete value works.
>
> Maybe I am missing something here with permissions... Should I be assigning
> group or specific user permissions on a field by field basis? Up until now I
> had only put users in groups and assigned group permissions to queues. I do
> have a couple nested groups as well, but no permissions explicitly defined
> on a per field basis. It seems like it should be working though since it
> does work for other field types, just not autocomplete.
>
>
>
>
>
> On Tue, Feb 28, 2012 at 10:46 AM, Ruslan Zakirov <ruz at bestpractical.com>
> wrote:
>>
>> Hi,
>>
>> Anything in debug logs when this doesn't work?
>>
>>
>> On Tue, Feb 28, 2012 at 19:38, Jim Lesinski <jim.lesinski at gmail.com>
>> wrote:
>> > The user (RTuser) is Privileged.
>> >
>> > Here is an outline of the permissions assigned to RTUser:
>> >
>> > RTUser is a member of a GroupA that has OwnTicket, StealTicket and
>> > TakeTicket rights on the queue1.
>> >
>> > GroupA is a member of GroupB, which has CommentOnTicket, CreateTicket,
>> > ReplyToTicket, Watch, SeeCustomField, SeeQueue, and ShowTicket
>> > permissions
>> > on queue1.
>> >
>> > To test permissions, I just now assigned every single permission to
>> > RTUser
>> > on the General Rights, Rights for Staff, and Rights for Administrators
>> > tabs
>> > to RTUser for queue1 and still the autocomplete values do not populate.
>> >
>> > If I go to Tools - Configuration - Global - User Rights and add RTUser
>> > and
>> > then check in "Do anything and everything", the autocomplete values work
>> > for
>> > groups.pm.
>> >
>> >
>> >
>> > On Tue, Feb 28, 2012 at 10:03 AM, Thomas Sibley <trs at bestpractical.com>
>> > wrote:
>> >>
>> >> On 02/28/2012 09:17 AM, Ruslan Zakirov wrote:
>> >> >> I have set up a custom data source for a custom field as outlined
>> >> >> in external_custom_fields.pod. It seems that everything works fine
>> >> >> and
>> >> >> I get
>> >> >> pick list data populated into the custom field for all field types
>> >> >> when
>> >> >> logged in as an account with root privileges. However, if I switch
>> >> >> to
>> >> >> an
>> >> >> account that has non-root privileges, all the fields types work as
>> >> >> expected
>> >> >> other than the autocomplete field type. For some reason this field
>> >> >> type
>> >> >> returns no data when I am logged in as a non-root user account.
>> >> [snip]
>> >> >> Has anyone else run into this? Can someone else verify this in their
>> >> >> environment?
>> >> >>
>> >> >
>> >> > http://issues.bestpractical.com/Ticket/Display.html?id=16946
>> >>
>> >> To clarify, that bug applies to Self Service (unprivileged) users only.
>> >>  It's not clear if your non-root user accounts that you tested with are
>> >> privileged or unprivileged.  If they are privileged, autocomplete CFs
>> >> should work just fine.
>> >>
>> >> Thomas
>> >> --------
>> >> RT Training Sessions (http://bestpractical.com/services/training.html)
>> >> * Boston  March 5 & 6, 2012
>> >
>> >
>> >
>> > --------
>> > RT Training Sessions (http://bestpractical.com/services/training.html)
>> > * Boston — March 5 & 6, 2012
>>
>>
>>
>> --
>> Best regards, Ruslan.
>
>



-- 
Best regards, Ruslan.