We recently migrated from on premise to Jira Cloud. In the on prem version, we were using Elements Connect pointed at a SQL server to retrieve a large list of part numbers. In on prem, that worked fine but now that we're in Cloud, the documentation says that it will only retrieve the first thousand rows that match what the user entered. So if they enter 1 into the field, Elements Connect only returns the first thousand records that start with a 1, not displaying any additional records. Does this mean we're limited to record sets of 1,000? Or does the query refresh once a second number is typed, e.g. User presses 1, first 1,000 records are returned that start with 1, then user presses 2 and the first 1,000 records are returned that start with 12, and on like that? I do not have access to the Dev environment and I'm not a Jira developer, I'm just trying to understand the limitations of the addon.
Thanks in Advance,
Josh
Hello @Scotto, Josh
Thanks for your question!
In Elements Connects, the query will refresh with each new character you type, allowing you to enter 2, 3, or more characters to find your desired option, regardless of the number of available options.
Technical detail: There is a 400ms debounce, which prevents excessive refreshing. If you type each new character within 400ms, it will only trigger a single request. For example, if you quickly type "123," we will search for results starting with "123" instead of sequentially searching for "1," then "12," and finally "123."
I hope this answers your question. Feel free to reach out if you need anything else!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.