Hi all,
I am little confused about RT's interpretation of Mandatory as
it relates to Custom Fields.
I have a CF's validation set to the canned regexp (?#Mandatory)
The CF in my test ticket has pointedly been left with no value.
Aside from a meager red warning on the page indicating it's not
On 07/10/2013 06:42 PM, Thomas Sibley wrote:
* What's unexpected is if a user has SeeCustomField, but not
ModifyCustomField on a mandatory CF, at ticket creation they get the
error MyCustomField: Input must match [Mandatory] even though it's not
displayed they don't have modify rights on it.
On 07/09/2013 05:08 PM, Tim Wiley wrote:
Not letting one group of users see a set of CFs is possible with RT's
rights, provided you haven't granted rights too widely at the global
level. You may need to rejigger some of your rights first to be less
global and more role/group/object specific.
On 07/10/2013 02:33 PM, Tim Wiley wrote:
I'm setting the validation field in the Basic CF config to (?#Mandatory).
Ok, good.
* What's unexpected is if a user has SeeCustomField, but not
ModifyCustomField on a mandatory CF, at ticket creation they get the
error MyCustomField: Input must match
GroupA are workers in effectively own Queue1. GroupA requested a
number of custom fields for their queue that help facilitate better
reporting on tickets. Because of the reporting nature of these custom
fields, GroupA has requested that only they have the permissions
required to set the
On 07/09/2013 02:20 PM, Tim Wiley wrote:
GroupA are workers in effectively own Queue1. GroupA requested a
number of custom fields for their queue that help facilitate better
reporting on tickets. Because of the reporting nature of these custom
fields, GroupA has requested that only they
On 07/09/2013 04:43 PM, Thomas Sibley wrote:
On 07/09/2013 02:20 PM, Tim Wiley wrote:
GroupA are workers in effectively own Queue1. GroupA requested a
number of custom fields for their queue that help facilitate better
reporting on tickets. Because of the reporting nature of these custom
Hello
I have some custom fields (mandatory and optional).
I would differentiate between mandatory and optional fields. I would add
a mark or something else near mandatory fields.
Is it possible ?
Thanks,
--
Alex
___
I have some custom fields (mandatory and optional).
I would differentiate between mandatory and optional fields. I would add
a mark or something else near mandatory fields.
Is it possible ?
Doesn't the system already do this in the italics below the field
name? If not, make a local version of
Alexandre,
Your question is odd. Are you saying you HAVE the CF's or WANT to have
some CF's?
Also, if a CF is defined as Mandatory, that is indicated when
creating/updating a ticket. This is explained in the RT Essentials book.
Kenn
LBNL
On 11/13/2009 7:40 AM, Alexandre PIASER wrote:
Hello
Will be fixed in 3.8.2 and 3.6.8 - patches are in the repo.
On Tue, Aug 19, 2008 at 1:53 PM, Monti gmail [EMAIL PROTECTED] wrote:
Hi,
I added a new custom field named Severiy with Type Select one value and
Validatione = Mandatory.
I want SelfService ticktes to be filled with the mandatory
Monti gmail wrote:
Hi,
I added a new custom field named Severiy with Type Select one value
and Validatione = Mandatory.
I want SelfService ticktes to be filled with the mandatory new custom
filed but it is not the case.
New ticket could be open without providing a value for my new
Stephen Steve,
Thanks a bunch, really. I'm just now learning some perl, so a lot of
stuff confuses me. I think I see it, so double thanks. You helped me fix
a problem AND taught me something.
Kenn
LBNL
On 3/11/2008 6:19 AM, Stephen Turner wrote:
At Monday 3/10/2008 05:10 PM,
On Tue, Mar 11, 2008 at 09:05:09AM -0700, Kenneth Crocker wrote:
Stephen Steve,
Thanks a bunch, really. I'm just now learning some perl, so a lot of
stuff confuses me. I think I see it, so double thanks. You helped me fix
a problem AND taught me something.
This provides a useful
Scott,
Very good. I'll get it.
Kenn
LBNL
On 3/11/2008 10:39 AM, Scott Lambert wrote:
On Tue, Mar 11, 2008 at 09:05:09AM -0700, Kenneth Crocker wrote:
Stephen Steve,
Thanks a bunch, really. I'm just now learning some perl, so a lot of
stuff confuses me. I think I see it, so
To all,
We have a Custom Field called Need-By Date. It is applied to only a
few Queues. In order to ensure the format entered is consistent, I put
the following (?#Date)^\d{2}/\d{2}/\d{4}$ into the Validation field.
The result is RT demands an entry as though it is a Mandatory Field.
At Monday 3/10/2008 12:31 PM, Kenneth Crocker wrote:
To all,
We have a Custom Field called Need-By Date. It is applied
to only a
few Queues. In order to ensure the format entered is consistent, I put
the following (?#Date)^\d{2}/\d{2}/\d{4}$ into the Validation field.
The result is RT
Stephen,
Why does yours have so much code? I just tried adding the '?' at the
end, in front of the '$' and it still doesn't work. Where would I make a
change to yours in order to get 4 positions for year?
Kenn
LBNL
On 3/10/2008 11:06 AM, Stephen Turner wrote:
At Monday 3/10/2008
18 matches
Mail list logo
