Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-46036

What is the real reason why SelectModel forces SingleSelect with attribute "multiple" ?

    XMLWordPrintable

Details

    • 6.02
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 06 November 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:

      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 – 06 November 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

      I am currently generalizing the usage of SingleSelect and MultiSelect in some customer plugins, where I was using only <select />;

      I have experienced some ClassCastException with all SingleSelect fields when I tries to retrieve the parameter.

      After some check in AUI Sources, I found that in SelectModel.js, the attribute "multilple" was applied explicitly for SingleSelect fields.

       if (this.type === "single") {
   this.$element.attr("multiple", "multiple");
}

      It causes that all Single Select value are passed systematically as a List of String instead of a simple String.

      For all SingleSelect for which I did an explicit call in my sources, I have added an explicit remove of this attribute.

      AJS.$($mySingleSelect.options.element).removeAttr("multiple");

      But when I the SingleSelect is built by initSingleUserPickers.js depending on js-default-user-picker class, there is no easy way to correct it.

      I experience this behavior with JIRA 6.2.7, but it seems to be more older and always present with JIRA 7.0.0.

      Questions :

      • Is this add of the multiple attribute is a bug or wanted ?
      • In such case, for which reason ?

      Attachments

        Issue Links

          links to

          Web Link Duplicates

          Activity

            People

              Unassigned Unassigned
              f910d4783680 Vincent Thoulé [Alkaes]
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: