Details
-
Bug
-
Resolution: Obsolete
-
Medium
-
None
-
4.2
-
firefox 3.6.11 (ubuntu), IE8, java 1.6.0_18, jira 4.2 standalone, tomcat 6
-
4.02
-
Severity 2 - Major
-
1
-
Description
After upgrade jira to 4.2 version I found out problem on report configuration screen. I have report with 2 select boxes in cascade:
... <property> <key>projectid</key> <name>report.cs.project</name> <description>report.cs.project.description </description> <type>select</type> <values class="com.atlassian.jira.portal.ProjectValuesGenerator"/> </property> <property> <key>version</key> <name>report.cs.version</name> <description>report.cs.version.description </description> <type>cascadingselect</type> <cascade-from>projectid</cascade-from> <values class="sk.eea.jira.plugin.report.ProjectsVersionCascadingValuesGenerator"/> </property> ....
Firefox 3.6.11 problem: There is no options in Projects selectbox and there are all versions of all projects in Version selectbox as you can see in attachment.
IE8 problem: There is no visible Version selectbox and navigation (Next, Cancel) buttons on screen as you can see at attachment.
Opera 10.63 and IE7 has no problem - everything works as before upgrade to jira 4.2.
I have done some research and I found out, that javascript function dynamicSelect(id1, id2) from cascadingutil.js is called with wrong parameters for firefox.
Firefox alert: "id1: undefined_select id2: projectid_select"
IE8 aler: "id1: projectid_select id2: version_select"
Opera alert: "id1: projectid_select id2: version_select"
In my opinion there is wrong resolving of hidden parameters paramCascadeFrom and paramName from <fieldset> elements of generated HTML code (html as attachment) in firefox.
Attachments
Issue Links
- relates to
-
JRASERVER-62823 CascadingSelect field type is broken in core reports
- Closed
- mentioned in
-
Page Loading...