Loading...

Details

Type: Bug
Resolution: Timed out
Priority: Low
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
- incomplete
- low-interest

Support reference count:
1
Bug Fix Policy:
View Atlassian Server bug fix policy
Current Status:
Hide

Atlassian Update – 11 October 2019

Hi everyone,

After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out.

Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy.

To see what the Jira team is currently working on and has recently delivered see the following dashboards:

Jira Server and Data Center: Recently resolved issues

Jira Server and Data Center: Current work and future plans

Jira Server and Data Center: Bug Fix Board

We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments.

Thank you,

Pawel Drygas,

Jira Server Bugmaster
Show
Atlassian Update – 11 October 2019 Hi everyone, After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out . Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy . To see what the Jira team is currently working on and has recently delivered see the following dashboards: Jira Server and Data Center: Recently resolved issues Jira Server and Data Center: Current work and future plans Jira Server and Data Center: Bug Fix Board We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments. Thank you, Pawel Drygas, Jira Server Bugmaster

Description

NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

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

Create a plugin that utilises the report plugin module.

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>
...

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.

Attachments

Issue Links

is related to

JRASERVER-22613 Cascading select doesn't work in firefox and ie8

Closed

relates to

JRACLOUD-62823 CascadingSelect field type is broken in core reports

Closed

is duplicated by: JSEV-326 Loading...

CascadingSelect field type is broken in core reports