-
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
[Dashboard][Event annotations][Lens] append postfix when duplicate title instead of interrupting save flow #161119
Comments
Pinging @elastic/kibana-presentation (Team:Presentation) |
Pinging @elastic/kibana-visualizations @elastic/kibana-visualizations-external (Team:Visualizations) |
@drewdaemon: Just to clarify, I'm not proposing that the duplicate name warning callout and the numeral suffix would be mutually exclusive; I'm just proposing that the populating of a name that is already in use not be the default experience (and the warning callout that comes with it). For example, based on your screenshot above, the numeral suffix would only be auto-populated if 1) the user hasn't altered the title to something unused and 2) the user turns on the switch to save as a new saved object. At the same time, if the user were to manually remove that numeral suffix or use some other existing saved object name, the warning callout should still indicate that fact to the user. |
@drewdaemon has there been any movement on this? Is it something that we should keep open do you think? |
@ThomThomson no movement, but still an actionable usability enhancement to consider. The ownership of that saved object modal is a little unclear. Technically Core for now, but they don't believe they should own it and won't make any changes there. So, it seems like it will probably be an analyst XP team or maybe shared UX. |
IMO this should be part of the UI phase of the Content Management project. These SO modals are very disjointed at the moment / spread out around many different plugins. |
Yeah, feels right to me. WDYT @vadimkibana ? Can we send this to SharedUX? |
Pinging @elastic/appex-sharedux (Team:SharedUX) |
Sending this to the shared ux team to decide if they want to keep it open or close it |
Triage on Feb 5th 2024 - Decided to keep it open but agree with Thom's CM comment. It will go into the icebox until CM gets more traction. |
…198777) ## Summary This PR fixes the issue with the [[Dashboard][Event annotations][Lens] appending a postfix when there is a duplicate title instead of interrupting the save flow](#161119). Currently, if a user wants to save an object as a new group without modifying the title, they will see a warning about it. This PR introduces an additional step. If the user attempts to save an object as a new group, we automatically append a postfix to the title. If the user manually changes the title back to the original and tries to save it, they will see the currently configured warning. https://github.com/user-attachments/assets/4f764b75-5b83-4277-8e5e-42fe1174fae7
…lastic#198777) ## Summary This PR fixes the issue with the [[Dashboard][Event annotations][Lens] appending a postfix when there is a duplicate title instead of interrupting the save flow](elastic#161119). Currently, if a user wants to save an object as a new group without modifying the title, they will see a warning about it. This PR introduces an additional step. If the user attempts to save an object as a new group, we automatically append a postfix to the title. If the user manually changes the title back to the original and tries to save it, they will see the currently configured warning. https://github.com/user-attachments/assets/4f764b75-5b83-4277-8e5e-42fe1174fae7 (cherry picked from commit b8dbf83)
…lastic#198777) ## Summary This PR fixes the issue with the [[Dashboard][Event annotations][Lens] appending a postfix when there is a duplicate title instead of interrupting the save flow](elastic#161119). Currently, if a user wants to save an object as a new group without modifying the title, they will see a warning about it. This PR introduces an additional step. If the user attempts to save an object as a new group, we automatically append a postfix to the title. If the user manually changes the title back to the original and tries to save it, they will see the currently configured warning. https://github.com/user-attachments/assets/4f764b75-5b83-4277-8e5e-42fe1174fae7
Describe the feature:
Today, when a user is about to save a piece of content with a duplicate title, they are interrupted by a warning. If they click "save" again after the warning is shown, they are allowed to save with a duplicate title.
In #152623 (comment), @MichaelMarcialis suggested
a new pattern in which no warning is shown and the save is allowed to occur with a postfix attached to the duplicate titleEdit: that we populate the title field with the existing title + postfix (e.g.my duplicate title [1]
) when the user selects "save as new."Today:
Not sure which team would take this (maybe SharedUX eventually)?
The text was updated successfully, but these errors were encountered: