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

Allow multi-select and multi-checkboxes custom field types to use auto-complete renderer

XMLWordPrintable

    • 18
    • 20
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      Atlassian Update - 22 April 2015

      Hi everyone,

      Thanks for voting and commenting on this issue. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with JIRA.

      At this time, this suggestion is not on the JIRA development roadmap. Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Regards,
      Dave Meyer
      dmeyer@atlassian.com
      Product Manager, JIRA Platform

      The application of the auto-complete renderer to the fix/affected versions field and components field is a welcome addition to Jira.
      What would be even more useful is if the auto-complete renderer could also be applied to any multi-select and/or multi-checkboxes custom field.
      We've got one particularly large multi-checkboxes custom field that has options added to it at a rate of 1 or 2 options a week. As it stands it causes major screen real estate problems when using "simple" searching.
      The "advanced" searching JQL auto-complete actually already offers auto-complete for the field in question, but for our less advanced users, we'd love to see something closer to the components/versions/labels auto-completion style in the simple searching (and general issue editing/moving) views.

      Workaround

      The multi select field renderer can be changed by enabling "multiselect.frother.renderer" dark feature

        1. auto-complete-edits.zip
          12 kB
        2. auto-complete-edits-5.2.zip
          10 kB
        3. multi-select.png
          multi-select.png
          22 kB

            [JRASERVER-23013] Allow multi-select and multi-checkboxes custom field types to use auto-complete renderer

            Björn Veith added a comment -

            Simply activate it in the dark features: https://confluence.atlassian.com/jirakb/how-to-manage-dark-features-in-jira-959286331.html

             

            Works perfectly

            Björn Veith added a comment - Simply activate it in the dark features: https://confluence.atlassian.com/jirakb/how-to-manage-dark-features-in-jira-959286331.html   Works perfectly

            Hamdy Atakora added a comment -

            multiselect.frother.renderer stopped working for us since version 8.12 or so

            Hamdy Atakora added a comment - multiselect.frother.renderer stopped working for us since version 8.12 or so

            Ann King added a comment -

            This feature will help provide ease of use for classification of data ; this in turn can be used as structured data for analysis and including in put for ML algorithms to help provide data insights.

            Ann King added a comment - This feature will help provide ease of use for classification of data ; this in turn can be used as structured data for analysis and including in put for ML algorithms to help provide data insights.

            Megha P added a comment -

            Hi @dmeyer@atlassian.com,

            As this feature is crucial for our banking customers, Please confirm what could be the risk of enabling dark features in Jira so that we could take the right decision and prepare for these risks.

             

            Thanks & Regards

            Megha

             

            Megha P added a comment - Hi @ dmeyer@atlassian.com , As this feature is crucial for our banking customers, Please confirm what could be the risk of enabling dark features in Jira so that we could take the right decision and prepare for these risks.   Thanks & Regards Megha  

            Tobias added a comment - - edited

            Hi Bjoern, 

            it worked to configure it, testing with Jira 8.13.x.

            Now i have to test if the functionality is right.

            Kind regards 

            Tobias 

            Tobias added a comment - - edited Hi Bjoern,  it worked to configure it, testing with Jira 8.13.x. Now i have to test if the functionality is right. Kind regards  Tobias 

            Bjoern Veith added a comment - - edited

            Hi Tobias, I just realised that my manual had a mistake. I copied it from our internal knowledge DB and since the important part of the URL was written bold those stupid * symbols were added. I corrected my previous comment, try again. Should work. 

             

            cheers

            Bjoern Veith added a comment - - edited Hi Tobias, I just realised that my manual had a mistake. I copied it from our internal knowledge DB and since the important part of the URL was written  bold those stupid * symbols were added. I corrected my previous comment, try again. Should work.    cheers

            StayAtHome added a comment - - edited

            It's strange, but multiselect.frother.renderer doesn't work in our Jira Server 8.13.0  

            StayAtHome added a comment - - edited It's strange, but  multiselect.frother.renderer doesn't work in our Jira Server 8.13.0  

            Tobias added a comment -

            Hi Bjoern, 

            thanks for your help.

            In my case the modified url throws a dead link  This doesn`t help in my opinion

            Tobias added a comment - Hi Bjoern,  thanks for your help. In my case the modified url throws a dead link  This doesn`t help in my opinion

            Bjoern Veith added a comment - - edited

            Corrected the URL

             

            Hey Tobias, it will not come,  so here is how you get the dark features: 

            1. login into your instance
            2. modify the url to: https://yourinstanceurl/secure/admin/SiteDarkFeatures!Default.jspa
            3. Enable "jira.site.darkfeature.admin" so you get a link to this page in Administration-menu
            4. Open the Dark feature menu and enter "multiselect.frother.renderer" into the text-field and klick add.

             

            greetings from Zürich

            Bjoern Veith added a comment - - edited Corrected the URL   Hey Tobias, it will not come,  so here is how you get the dark features:  login into your instance modify the url to: https://yourinstanceurl/secure/admin/SiteDarkFeatures!Default.jspa Enable "jira.site.darkfeature.admin" so you get a link to this page in Administration-menu Open the Dark feature menu and enter "multiselect.frother.renderer" into the text-field and klick add.   greetings from Zürich

            Tobias added a comment -

            334 votes and nothing happens...guys are you serious? This should be a default setting. I don´t have the SiteDarkFeatures!default.jspa in my config. Use Jira 8.5.8 with over 2000 users, so why can´t you fix this?!

            Tobias added a comment - 334 votes and nothing happens...guys are you serious? This should be a default setting. I don´t have the SiteDarkFeatures!default.jspa in my config. Use Jira 8.5.8 with over 2000 users, so why can´t you fix this?!

              Unassigned Unassigned
              b0d88db9bee7 David Corley
              Votes:
              399 Vote for this issue
              Watchers:
              197 Start watching this issue

                Created:
                Updated: