Summary

The cascadingselect field type does not work in the reports plugin module. A plugin attempting to use this field type will compile without problems, but no select input field will be rendered in the final report.

Environment

• JIRA 7.2.3;
• OSX 10.11.2;
• Chrome 53.0.2785.143.

Steps to Reproduce

1. Create a plugin that utilises the report plugin module.
2. Define a new report in the atlassian-plugin.xml, and specify a cascadingselect field type (example below):

   ...
   <property>
     <key>selectForCascade</key>
     <name>Select for cascade</name>
     <description>First part of the cascading field</description>
     <type>select</type>
     <values>
       <value>
         <key>happy</key>
         <value>Happy</value>
       </value>
       <value>
         <key>sad</key>
         <value>Sad</value>
       </value>
     </values>
   </property>
   <property>
     <key>aCascade</key>
     <name>Cascade select field</name>
     <description>Secondt part of the cascading field</description>
     <type>cascadingselect</type>
     <cascade-from>selectForCascade</cascade-from>
     <values>
       <value>
         <key>cat</key>
         <value>Cat</value>
       </value>
       <value>
         <key>dog</key>
         <value>Dog</value>
       </value>
     </values>
   </property>
   ...
   
   
   
   
   

1. Navigate to the custom report.

Expected Results

Two select fields should be present on the configure report screen (hardcoded values in the second select should come from a ValuesGenerator that depends on the value of the first select).

Actual Results

No input field is rendered at all for the second select, and if a ValuesGenerator was used to populate the second select, it is never executed.  

Workaround

According to this Confluence Question, the eazyBI Reports Plugin can provide this functionality.