We need your help with a workaround solution for the Cascading Select fields, especially when they have too many entries and need to perform CRUD operations.
The Edit page is loading very slow, in fact, it's using the browser's RAM and shutting down. I was able to write some programmatical code for to Create, Delete, Enable and, Disable methods. But didn't find any docs/community support pages to give us a clue on updates (like renaming these options). Etc.
Please suggest a workaround solution and best practices follow moving forward.
There is nothing you can do with this, other than re-work your data into a sensible usable shape.
The problem is this long select list is breaking your page load. Behaviours can't help you - they run after the page has been loaded.
You shouldn't be using a select list that has more than a couple of hundred options, it doesn't work for the humans and it doesn't work in the browser.
Your only option is to question why you've got far too many useless options in your list and work out a different way to do it.
How many values to you have in the top level select? And is there anyway to group those values into smaller subset? So, I guess I should ask what type of data is in the top select?
Another option might be to use ProForma forms to put in some conditional logic for the values.
Hi @John M Funk
We have this Single List Cascading field as
"Field Name" -
2 Parent Options -
Parent Option1 - 6400 Entries, (Single Custom Field Context)
Parent Option 2 - 1600 Entries. (Single Custom Field Context)
It makes sense of why the page is loading really slow and sometimes it never loads. Yes, I worked on a scenarios to subset them... but I faced an issue, when I tried using custom field contexts to split these 6400 entries into 6399 into custom field context1, 1 entry into custom field context2. All I see in the dropdowns is only one entry and the rest 6399 entries in the other context are hidden. Is there a formula/template you can suggest to subset them into? The other scenarios I am thinking is once if I was able to subset them, I can write some behaviors to show them in drop downs on view screen by their 1st alphabetical order. Yes, we will try ProForma, but do not know our organization would add some more dollars to purchase this plugin.
Sure, but can you help on arranging the subsets of these 6K+ records with the same custom field contexts? So it will be easier to edit and display.. within the custom field configuration page.. and once these are completed sub setting, I can apply behavior on top of it.
👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events