-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Fix "Assign object to spaces" flyout UX problems #128946
Fix "Assign object to spaces" flyout UX problems #128946
Conversation
* Now renders each space as checked * Now shows all spaces even if the feature is disabled there * Now hides "Need additional privileges" tooltip icons * Adds "total spaces" count
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for fixing these! I just had one more suggestion where it was a bit of an odd layout.
.../plugins/spaces/public/share_saved_objects_to_space/components/selectable_spaces_control.tsx
Outdated
Show resolved
Hide resolved
…sign-to-spaces-flyout
Now the number is inline with the text below the space selector.
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
changes look good and work well!
ACK: will review today |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code LGTM and everything seems to work as expected, thanks for the detailed "testing" steps!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for fixing these! I checked in Chrome, FF, and Safari. I also double checked some of the different privilege scenarios. I didn't come across any more obvious bugs.
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
(cherry picked from commit 19e43a3)
Resolves #128916.
This PR makes several changes to the "Assign object to spaces" flyout.
Testing
Minimal privilege testing:
Click to see script to create 26 extra spaces
Screen recording
In this example, an ML job was created in the Default space and then added to the Bravo space.
After that, the ML feature was disabled in the Bravo and Charlie spaces.
When the user views the "Assign object to spaces" flyout for this job:
Screen.Recording.2022-03-30.at.11.46.42.AM.mov
Screenshots
Minimally-privileged user ("Read" access to Bravo, and "All" access to 10 other spaces) viewing an object that has been assigned to All spaces:
The same user viewing the same object after someone else has changed its assignment to only the Default space (now the "Need more privileges" tooltip icon is displayed):
Viewing the flyout with a narrow viewport:
Viewing the flyout with a short viewport (the spaces list has a minimum height, and an additional vertical scroll bar appears):
When the user only has Read access in the active space, they cannot click on the space list:
When the object is shared to additional spaces that the user doesn't have access to view, the number of hidden spaces is now shown below the space selector: