-
Suggestion
-
Resolution: Unresolved
-
None
-
Standalone, JDK 1.6.0_15, Centos 5.5
-
70
-
39
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
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
- is duplicated by
-
- Closed
-
- Closed
- is related to
-
- Closed
- relates to
-
- Closed
-
- Gathering Interest
-
- Gathering Interest
| Support reference count | Original: 38 | New: 39 |
| UIS | Original: 53 | New: 70 |
| Support reference count | Original: 20 | New: 38 |
| UIS | Original: 35 | New: 53 |
| UIS | Original: 18 | New: 35 |
| UIS | Original: 37 | New: 18 |
| UIS | Original: 18 | New: 37 |
| UIS | Original: 19 | New: 18 |
| UIS | Original: 18 | New: 19 |
| Description |
Original:
{panel:bgColor=#e7f4fa}
*NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-23013]. {panel} {panel:title=Atlassian Update - 22 April 2015|borderStyle=solid|borderColor=#ebf2f9|titleBGColor=#ebf2f9|bgColor=#ffffff} 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|https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com]. 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|mailto:dmeyer@atlassian.com] Product Manager, JIRA Platform {panel} 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. h3. Workaround The multi select field renderer can be changed by enabling "multiselect.frother.renderer" [dark feature|https://jira.atlassian.com/secure/admin/SiteDarkFeatures!Default.jspa] |
New:
{panel:bgColor=#e7f4fa}
*NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-23013]. {panel} {panel:title=Atlassian Update - 22 April 2015|borderStyle=solid|borderColor=#ebf2f9|titleBGColor=#ebf2f9|bgColor=#ffffff} 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|https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com]. 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|mailto:dmeyer@atlassian.com] Product Manager, JIRA Platform {panel} 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. h3. Workaround The multi select field renderer can be changed by enabling "multiselect.frother.renderer" [dark feature|https://confluence.atlassian.com/jirakb/how-to-manage-dark-features-in-jira-959286331.html] |