-
Notifications
You must be signed in to change notification settings - Fork 13k
fix: Disabled sorting for non-indexed columns in Omnichannel Contact Center #36100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Looks like this PR is ready to merge! 🎉 |
🦋 Changeset detectedLatest commit: edec0f8 The changes in this PR will be included in the next version bump. This PR includes changesets to release 36 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #36100 +/- ##
========================================
Coverage 64.43% 64.43%
========================================
Files 3138 3139 +1
Lines 104920 104927 +7
Branches 19783 19806 +23
========================================
+ Hits 67600 67607 +7
- Misses 34632 34635 +3
+ Partials 2688 2685 -3
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
8b256bd to
bf5f677
Compare
bf5f677 to
667d56b
Compare
Proposed changes (including videos or screenshots)
Most columns in the Contact Center table don't have indexes that support efficient sorting. Sorting on these columns can slow down the system and put extra load on the database. Taking up to 1min initial load for some workspaces.
To improve performance and avoid unnecessary database work, sorting is now only allowed on the "Name" and "Started at" columns, which do have proper indexes.
Issue(s)
CTZ-102
Steps to test or reproduce
Further comments
If we identify a need for sorting on other columns in the future, we’ll plan and implement it properly with the necessary database support.