Bug #83976 for RT-Extension-MandatoryOnTransition: Ticket Custom Fields

Fri Mar 15 14:17:08 2013 Chris.Wolfrom [...] salemfive.com - Ticket created

Subject:	Ticket Custom Fields
Date:	Fri, 15 Mar 2013 14:16:51 -0400
To:	<bug-RT-Extension-MandatoryOnTransition [...] rt.cpan.org>
From:	<Chris.Wolfrom [...] salemfive.com>

Hello, I was attempting to make a ticket custom field mandatory when the ticket is resolved and ran into this issue. With the configuration that follows, the "TimeWorked" field is made mandatory, but the "CF.MyField" custom field is not. Set( %MandatoryOnTransition, Helpdesk => { '* -> resolved' => ['TimeWorked', 'CF.MyField'], }, ); Since the custom field was a ticket custom field I tried changing the prefix from "CF" to "TicketCF". This resulted in making all of the ticket custom fields mandatory instead of just the one I specified. Set( %MandatoryOnTransition, Helpdesk => { '* -> resolved' => ['TimeWorked', 'TicketCF.MyField'], }, ); I may be doing something incorrectly, but thought I would report it anyway. All-in-all still a good extension as it was the "TimeWorked" field I was after in the first place. Regards, Chris Wolfrom Enterprise Solutions Architect Salem Five Bank (e) chris.wolfrom@salemfive.com<mailto:chris.wolfrom@salemfive.com> (p) 978.720.5383 (f) 978.498.0312

Thu Mar 21 14:23:00 2013 trs [...] bestpractical.com - Correspondence added

Subject:	Re: [rt.cpan.org #83976] Ticket Custom Fields
Date:	Thu, 21 Mar 2013 11:22:58 -0700
To:	bug-RT-Extension-MandatoryOnTransition [...] rt.cpan.org
From:	Thomas Sibley <trs [...] bestpractical.com>

On 03/15/2013 11:17 AM, Chris.Wolfrom via RT wrote: Show quoted text

> I was attempting to make a ticket custom field mandatory when the ticket is resolved and ran into this issue. With the configuration that follows, the "TimeWorked" field is made mandatory, but the "CF.MyField" custom field is not. > > Set( %MandatoryOnTransition, > Helpdesk => { > '* -> resolved' => ['TimeWorked', 'CF.MyField'], > }, > );

Is your custom field actually named "MyField"? If so, the above should work. Otherwise, you need to use the actual name of your CF. This extension works in production on a number of RT instances and tests pass, so I suspect your problems are a configuration error. Show quoted text

> Since the custom field was a ticket custom field I tried changing the > prefix from "CF" to "TicketCF". This resulted in making all of the > ticket custom fields mandatory instead of just the one I specified.

I'm very skeptical that all of the CFs were made mandatory by spelling "CF" as "TicketCF". I suspect you're mistaken. Note that "TicketCF" will never work and isn't documented anywhere.

Thu Mar 21 14:23:01 2013 The RT System itself - Status changed from 'new' to 'open'

Thu Mar 21 14:23:09 2013 tsibley [...] cpan.org - Status changed from 'open' to 'rejected'

Fri Mar 22 11:14:09 2013 Chris.Wolfrom [...] salemfive.com - Correspondence added

Subject:	RE: [rt.cpan.org #83976] Ticket Custom Fields
Date:	Fri, 22 Mar 2013 11:13:53 -0400
To:	<bug-RT-Extension-MandatoryOnTransition [...] rt.cpan.org>
From:	<Chris.Wolfrom [...] salemfive.com>

No, the custom field is named "Issue Type". I was only using "MyField" to be clear. The actual directive in my RT_SiteConfig file is: Set( %MandatoryOnTransition, 'Help Desk' => { '* -> resolved' => ['TimeWorked', 'CF.Issue Type' ], }, ); Show quoted text

-----Original Message----- From: trs@bestpractical.com via RT [mailto:bug-RT-Extension-MandatoryOnTransition@rt.cpan.org] Sent: Thursday, March 21, 2013 2:23 PM To: Wolfrom, Chris Subject: Re: [rt.cpan.org #83976] Ticket Custom Fields <URL: https://rt.cpan.org/Ticket/Display.html?id=83976 > On 03/15/2013 11:17 AM, Chris.Wolfrom via RT wrote:

> I was attempting to make a ticket custom field mandatory when the ticket is resolved and ran into this issue. With the configuration that follows, the "TimeWorked" field is made mandatory, but the "CF.MyField" custom field is not. > > Set( %MandatoryOnTransition, > Helpdesk => { > '* -> resolved' => ['TimeWorked', 'CF.MyField'], > }, > );

Is your custom field actually named "MyField"? If so, the above should work. Otherwise, you need to use the actual name of your CF. This extension works in production on a number of RT instances and tests pass, so I suspect your problems are a configuration error.

> Since the custom field was a ticket custom field I tried changing the > prefix from "CF" to "TicketCF". This resulted in making all of the > ticket custom fields mandatory instead of just the one I specified.

I'm very skeptical that all of the CFs were made mandatory by spelling "CF" as "TicketCF". I suspect you're mistaken. Note that "TicketCF" will never work and isn't documented anywhere.

Fri Mar 22 11:14:10 2013 The RT System itself - Status changed from 'rejected' to 'open'

Tue Mar 26 18:29:52 2013 trs [...] bestpractical.com - Correspondence added

Subject:	Re: [rt.cpan.org #83976] Ticket Custom Fields
Date:	Tue, 26 Mar 2013 15:29:49 -0700
To:	bug-RT-Extension-MandatoryOnTransition [...] rt.cpan.org
From:	Thomas Sibley <trs [...] bestpractical.com>

On 03/22/2013 08:14 AM, Chris.Wolfrom via RT wrote: Show quoted text

> No, the custom field is named "Issue Type". I was only using "MyField" to be clear. The actual directive in my RT_SiteConfig file is: > > Set( %MandatoryOnTransition, > 'Help Desk' => { > '* -> resolved' => ['TimeWorked', 'CF.Issue Type' ], > }, > );

That should work just fine and a similar setup is in our unit tests for this extension. My only guess without more info is that it's a permissions issue around the ShowCustomField/ModifyCustomField rights on your system. If you try as root or another RT superuser, is it different? What ticket page are you trying this on? Thomas

Tue Mar 26 18:30:53 2013 tsibley [...] cpan.org - Status changed from 'open' to 'rejected'