Load single select options lazily, not to slow down the UI


When having an issue field with over 10k options, the UI searching slows down significantly. We should change the rendering to lazily load options. (Could depend on the number of options to be shown)




David Younger
July 10, 2019, 11:25 PM

Can Jira please look at this issue. It is affecting a lot of people and runining what is an essential add-on product (Atlas CRM).



Alamos GmbH
December 20, 2018, 9:43 AM

We also need this functionality. We are using Atlas CRM to manage which service contract a customer has and we need this information in JQL for SLA's to set the corresponding times.

Jonathan Zschau
April 2, 2018, 9:01 PM

We're really looking forward to this as other JIRA Cloud plugins such as Tempo and CRM for JIRA have the ability to add a field that behaves this way. We need to be able to designate a customer on issue creation and having a simple Account/Customer field available on issue creation is critical. This is the only thing holding us back from this plugin. If I'm missing something let me know, but from the conversations I've had it sounds as if the process for linking issues to a customer in AtlasCRM requires going back to the issue and linking them to it, which is not as intuitive as simply having the ability to choose the customer on issue creation.

Dave Meyer
February 26, 2018, 11:33 PM

Hey ,

Yes, we don't have a timeline right now but we do plan to address this as part of a larger investment in Jira Cloud performance.


Mitchel Kuijpers
February 21, 2018, 8:21 AM

Are there any plans to fix this issue? We (atlas-crm) would love to move to issue fields. But this is currently a blocker for us. We have customers with a lot more then 10k items and we don't want to break their issue search screen.




Bartlomiej Lewandowski