Here are the queries I used to verify the custom field data:

– child
select distinct
(select customValue from customfieldoption where id = cfo.parentoptionid) as parentOption,
cfo.*,
'------',
cv.*,
'------',
cf.*
from
customfieldoption cfo, customfieldvalue cv, customfield cf
where
cv.customfield = 10102 and – application component
– cv.issue = issueId and
cv.customfield = cfo.customfield and
cfo.id = to_number(cv.stringvalue) and
cf.id = cv.customfield and
cv.parentkey is not null
order by cfo.parentoptionid, cfo.customvalue

– parent?

select
cfo.*,
'------',
cv.*,
'------',
cf.*
from
customfieldoption cfo, customfieldvalue cv, customfield cf
where
cv.customfield = 10102 and
– cv.issue = issueId and
cv.customfield = cfo.customfield and
cfo.id = to_number(cv.stringvalue) and
cf.id = cv.customfield and
cv.parentkey is null
order by cfo.customvalue

should include 10114, 10115, 10117, etc, but only include 'none' and 'please select'

It is clear in the attachment that the fields are in the html

Verified same behavior with IE 6.0.28.00.1106.xpsp2.030618-0119

Sorry about the delay. The problem lies with making the cascading select mandatory in 3.0.2 (see JRA-5010). The immediate workaround is not make cascading fields not mandatory. This will allow acceptable data to be entered in your system immediately.

You should then upgrade to 3.0.3 immediately. Please let us know how this goes, especially if the workaround still does not work.

Cheers

Mark C