CustomField input must match formatting in edit

RT Users
1

I’ve noticed this in both IE and FireFox. I’m running 4.0.4.

When editing a ticket that has custom fields with validation (mandatory), some of them display the “Input must match…” under the CF name, not the entry.

For example (hopefully this will format right on the listserv), if I have a select 1 value dropdown, it will look like this:

CF Name <>
Select one value
Input must match [Mandatory]

In other types of fields, like a text area, it looks like this:

CF Name <>
Select one value <>

Input must match [Mandatory]

Actually, it looks like “select one value” is the only one that formats that way, which when I look at it, looks correct/clean. When it’s shifted left, to me anyways, it implies the field below, not above, is mandatory.

I tried monkeying with the CSS to see if I could get it to place right, but it didn’t. I’m not sure which is the intended way for it to format, but it’d be nice to either be able to change it, or at least have it consistent for all field types.

Maybe a different topic, but while debugging the formatting above, I noticed if I use a * in a custom field validation (ie: I want to allow the field to contain only digits or be empty, so I modified the regex from ^[\d.]+$ to ^[\d.]*$), the validation works, but it doesn’t display the “Input must match…” text at all.

Thanks!
Brent

2

Hi,

A screenshot would be helpful.On Tue, Feb 7, 2012 at 02:46, Brent Wiese bwiese@elementps.com wrote:

I’ve noticed this in both IE and FireFox. I’m running 4.0.4.

When editing a ticket that has custom fields with validation (mandatory),
some of them display the “Input must match…” under the CF name, not the
entry.

For example (hopefully this will format right on the listserv), if I have a
select 1 value dropdown, it will look like this:

CF Name <>

Select one value

                                                            <red

italics>Input must match [Mandatory]

In other types of fields, like a text area, it looks like this:

CF Name
<>

Select one value <>

Input must match [Mandatory]

Actually, it looks like “select one value” is the only one that formats that
way, which when I look at it, looks correct/clean. When it’s shifted left,
to me anyways, it implies the field below, not above, is mandatory.

I tried monkeying with the CSS to see if I could get it to place right, but
it didn’t. I’m not sure which is the intended way for it to format, but it’d
be nice to either be able to change it, or at least have it consistent for
all field types.

Maybe a different topic, but while debugging the formatting above, I noticed
if I use a * in a custom field validation (ie: I want to allow the field to
contain only digits or be empty, so I modified the regex from [1]+$ to
[2]*$), the validation works, but it doesn’t display the “Input must
match…” text at all.

Thanks!

Brent

RT Training Sessions (http://bestpractical.com/services/training.html)

  • Boston — March 5 & 6, 2012

Best regards, Ruslan.

  1. \d. ↩︎

  2. \d. ↩︎

3

Sorry, wasn’t sure if a screenshot would come through on the list.

Attached.

   Brent Wiese
    Direct Number: (480) 993-0788
    Mobile Number: (480) 286-6557From: ruslan.zakirov@gmail.com [mailto:ruslan.zakirov@gmail.com] On Behalf Of Ruslan Zakirov

Sent: Monday, February 06, 2012 3:55 PM
To: Brent Wiese
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] CustomField input must match formatting in edit

Hi,

A screenshot would be helpful.

4

Sorry, wasn’t sure if a screenshot would come through on the list.

The layout of that field could use some loving, it has a CSS class
these days so it should be much easier to do things to it:
cfinvalidfield

Maybe a different topic, but while debugging the formatting above, I
noticed if I use a * in a custom field validation (ie: I want to allow
the field to contain only digits or be empty, so I modified the regex
from [1]+$ to [2]*$), the validation works, but it doesn’t
display the “Input must match…” text at all.

RT decides whether or not display the hint by validating all the CFs
at page render time. This means that since * matches the empty field,
it doesn’t have an error hint to show.

Frankly - it’d probably be a lot better if we just started showing the
Description of Custom Fields as a Hint box on 4.2.

-kevin

  1. \d. ↩︎

  2. \d. ↩︎