Hello,
Custom fields do not work after migrating from version 4.2.0 to 4.2.12 release,
tickets are not updated.
The logs indicate nothing , no trace of activies for custom fields .
An idea of what it may come ?
In advance thank you for your help
Horst
Hi,
On Mon, Jan 25, 2016 at 7:45 AM, Kriegers Horst wrote:
> Hello,
>
>
>
> Custom fields do not work after migrating from version 4.2.0 to 4.2.12
> release, tickets are not updated.
That shouldn't be the case. Do you have any JS or callbacks that would
be "interfering"
On 04.03.2014 06:49, Biju Chacko wrote:
> Chris Herrmann gmail.com> writes:
>> Hi guys,
>>
>> Just wondering if there are any plugins or ?? That would
>> facilitate alternative ways of visualising "work
>> to do" like agile or kanban or ??
>>
>> I'm thinking this could be helpful for teams
>>
HI Sally,
Thanks for your input.
My overall goal is to make it easy for another team member to take over
another's work while they are away. Since each person is using the same
dashboard all based on __CurrentUser__, only someone logged in as user X
can see user X's tickets.
Your idea of
Show the calls to rt-mailgate from your configuration file(s).
On Sat, Jan 23, 2016 at 11:51 PM, Dumitru Catalin
wrote:
> Yes, i use rt-mailgate and postfix, and i set the corresponding alias in
> /etc/aliases
>
> În sâm., 23 ian. 2016 la 21:08, Ram
Greetings,
I can populate my Users from my customer list through the REST Interface.
I have some custom fields like IDNumber and others...
I've tried like that:
CF.{IDNumber} = 999888
and
CF- IDNumber = 999888
And
CF-'IDNumber' = 999888
The user was created! But were not filled. I have the
Has anyone ever attempted to integrate RT with DataDog and it's web api or
configurations?
I've seen some integrations with "SendNagiosAlert" but was wondering if
anyone had done something similar with DataDog? I'm starting to play with
it now using this -
Hey,
On Wed, 2016-01-20 at 08:28 -0600, Matt Zagrabelny wrote:
> I don't believe the 1.0 REST API supports txn CFs.
>
> Some options are:
>
> * Hack together something for the 1.0 REST.
> * Totally bypass the REST and do something via perl executables and
> ssh.
> * Try out the new REST