Someone in private pointed me to his book, and mentioned permissions. Then I figured it out, dummy me. Of course, rights.
rt-mailgate "authenticates" as an user created out of the mails's FROM address [1]. And that's an unprivileged user. I tried several ways, and it only worked giving ModifyCustomField e SeeCustomField rights to unprivileged users (I did this only for one particular customfield I need the default to be set on arrival). This seems like an excellent use case for the new SetInitialCustomField right that came in 4.4.1, that would be more restricted, but setting or unsetting it does not make any difference for my case. Can someone tip me if this is a bug, feature request, or maybe still some wrong config of my part? [1] https://docs.bestpractical.com/rt/4.4.1/RT/Interface/Email/Auth/MailFrom.html Diego Morales Fones: +55 51 3024-3568 | +55 11 4063-8864 Propus - TI alinhada a negócios Service | Telecom | Tech | Data Science www.propus.com.br On Mon, Aug 29, 2016 at 7:15 PM, Diego Morales <mora...@propus.com.br> wrote: > Hello, > > I am using RT 4.4.1, setting a default value for a Custom Field, and that > seems to be ignored when the ticket is created via email (rt-mailgate). > > It does work when I create a ticket using the API, for example (via > python-rt). I have logs on debug level and see no errors about it. > > Does anybody there confirm that? Or is it something in my setup? I tried > disabling all plugins, and made no difference. > > Thanks in advance. > > Diego Morales > Fones: +55 51 3024-3568 | +55 11 4063-8864 > Propus - TI alinhada a negócios > Service | Telecom | Tech | Data Science > www.propus.com.br > >
--------- RT 4.4 and RTIR training sessions, and a new workshop day! https://bestpractical.com/training * Boston - October 24-26 * Los Angeles - Q1 2017