[#JRA-5010] "None" is still selectable in a cascading select custom field despite being set to required

JIRA

"None" is still selectable in a cascading select custom field despite being set to required

Created: 21/Oct/04 02:59 PM Updated: 30/Jul/06 07:35 PM

Component/s:

Custom Fields (new types)

Affects Version/s:

3.0.1

Fix Version/s:

3.2

Time Tracking:

Not Specified

Issue Links:

Reference

This issue is related to:

~~JRA-5657~~ Cascading select - parent/child mismatched on edit/create screen

Participants:	Dan Haynes, Jeff Turner [Atlassian], Keith Brophy and Mark Chaimungkalanont [Atlassian]
Since last comment:	3 years, 13 weeks, 6 days ago
Resolution Date:	24/May/05 12:31 AM
Labels:

Description

« Hide

I create the following casacading select:

List 1
option1.1
option1.2
option1.3
List 2
option2.1
option2.2
option2.3
List 3
option3.1
option3.2
option3.3

When I create an issue everything is fine. I then make this a required field I then see the following at issue creation:

List 1
none
List 2
none
option1.1
option1.2
option1.3
List 3
none
option2.1
option2.2
option2.3

I can switch back and forth between making the field required and optional. Whenever it is optional everything is fine. Whenever it is required I get the above.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Jeff Turner [Atlassian] added a comment - 25/Oct/04 02:45 AM

I can confirm this behaviour. I guess we should be removing the 'None' option if the field is required.

Thanks for the report

[ Permlink | « Hide ]

Mark Chaimungkalanont [Atlassian] added a comment - 27/Oct/04 07:49 PM

This will be fixed in 3.0.3 for Firefox. In IE, the options will no longer be messed up (so the fields will be usable at least) but "None" is still a valid option.

[ Permlink | « Hide ]

Mark Chaimungkalanont [Atlassian] added a comment - 16/Jan/05 06:20 PM

A must fix for 3.1. Or at the very least, copy the workaround into the main branch. Currently only committed in the 3.0.x branch

[ Permlink | « Hide ]

Keith Brophy added a comment - 16/Mar/05 07:21 PM

The problem described in the summary is still not fixed.

[ Permlink | « Hide ]

Mark Chaimungkalanont [Atlassian] added a comment - 24/May/05 12:31 AM

The "None" value can now always be selected (consistent with other fields). A validation occurs that forces a value to be entered.