We are using Idalko multi level cascade field and created 7 levels in the field.
The level are dependent on each other.
The issue im facing is the query is getting long level by level.
Its take time to load values on the screen because of long queries.
Can anyone help me to reduce the queries so it will take less time to load on the screen.
You've quite simply got too many levels in there. Why are you doing this? Reading the names of the levels across the top of the definition, tells me you're building a totally unwieldy and pretty much useless flat field from a load of things that should not be done as drop-down.
What would the purpose of this field be? What benefits would the end user get from being able to select at this level? Do you really identify individual items of data by their version, description, task etc?
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
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