Custom field mandatory

Hello

I’ve re 3.8.8.
Data base is oracle.

I’ve a problem with mandatory custom field.

When i create ticket from the web it’s all ok. When mandatory custom filed it’s empty a get “Input must match [Mandatory]”
But when i create ticket from email i could write comments/corespondence, change the queue, without any warning.

  • It’s happen to all queue, to all mandatory custom field
  • custom filed is type “select one vaule”
  • when i add new custom filed mandatory it’s the same problem.
  • line from /etc/aliases
    admin: |“/opt/rt3/bin/rt-mailgate --queue Admin --action correspond --url http://rt.domain.com/

Lukas

When i create ticket from the web it’s all ok. When mandatory custom filed it’s empty a get “Input must match [Mandatory]”
But when i create ticket from email i could write comments/corespondence, change the queue, without any warning.

RT’s custom fields are only Mandatory in the UI. There is no core way
to set Custom Fields during email creation, even if there was, we’d
have to bounce emails saying “use this arcane format to set some
custom fields for your support request”?

You may be interested in this to ensure CFs are set prior to a ticket
being resolved.

-kevin

Hello

I don’t want to set custom field from email.
I have problem when ticket is created from email, and next when i click in the web page, mandatory filed is not mandatory, i could leave they empty and write comment or change queue
That is the problem.

Thanks for RT-Extension-MandatoryOnTransition i’ll check this.

Lukas-----Original Message-----
From: rt-users [mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Kevin Falcone
Sent: Tuesday, June 17, 2014 9:00 PM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] custom field mandatory

On Mon, Jun 16, 2014 at 11:47:10AM +0000, Zawada Łukasz wrote:

When i create ticket from the web it’s all ok. When mandatory custom filed it’s empty a get “Input must match [Mandatory]”
But when i create ticket from email i could write comments/corespondence, change the queue, without any warning.

RT’s custom fields are only Mandatory in the UI. There is no core way to set Custom Fields during email creation, even if there was, we’d have to bounce emails saying “use this arcane format to set some custom fields for your support request”?

You may be interested in this to ensure CFs are set prior to a ticket being resolved.

-kevin

RT-Extension-MandatoryOnTransition it’s not working on rt 3.8.8

I set
Set( %MandatoryOnTransition,
’ => {
→ resolved’ => ‘CF.Typ’,
},
);

Log on debug say nothing-----Original Message-----
From: rt-users [mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Kevin Falcone
Sent: Tuesday, June 17, 2014 9:00 PM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] custom field mandatory

On Mon, Jun 16, 2014 at 11:47:10AM +0000, Zawada Łukasz wrote:

When i create ticket from the web it’s all ok. When mandatory custom filed it’s empty a get “Input must match [Mandatory]”
But when i create ticket from email i could write comments/corespondence, change the queue, without any warning.

RT’s custom fields are only Mandatory in the UI. There is no core way to set Custom Fields during email creation, even if there was, we’d have to bounce emails saying “use this arcane format to set some custom fields for your support request”?

You may be interested in this to ensure CFs are set prior to a ticket being resolved.

-kevin

RT-Extension-MandatoryOnTransition it’s not working on rt 3.8.8

Ah, you didn’t say you were using an unsupported release of RT.

I set
Set( %MandatoryOnTransition,
’ => {
-> resolved’ => ‘CF.Typ’,
},
);

I’m surprised you were able to install it, it should die during the
installation saying “You must have at least RT 4.0.0 to run this”.

You can implement the code in the extension as overlays on 3.8, but
the extension does not support 3.8.

-kevin