Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Saving a visualization with the same name does not overwrite #19734

Closed
PadreZippo opened this issue Jun 7, 2018 · 2 comments
Closed

Saving a visualization with the same name does not overwrite #19734

PadreZippo opened this issue Jun 7, 2018 · 2 comments
Labels
Feature:Visualizations Generic visualization features (in case no more specific feature label is available) Team:Visualizations Visualization editors, elastic-charts and infrastructure triage_needed

Comments

@PadreZippo
Copy link

Kibana version:
4.6.6

Elasticsearch version
2.4.6

Describe the bug:
When saving a visualization with the same name as an existing visualization, it throws the warning "Are you sure you want to overwrite....". However, after confirming, the visualization is not overwritten; you are left with two visualizations with the same name.

Steps to reproduce:

  1. Create a visualization
  2. Edit it, or create a new visualization
  3. Save it with the same name and confirm overwrite

→ You now have two visualizations with the same name

Expected behavior:

The original visualization should be overwritten.
@Bargs Bargs added Feature:Visualizations Generic visualization features (in case no more specific feature label is available) triage_needed labels Jun 12, 2018
@cjcenizal
Copy link
Contributor

cjcenizal commented Jul 16, 2018 •
edited
Loading

This is also happening on master (7.0.0).

@timroes timroes added the Team:Visualizations Visualization editors, elastic-charts and infrastructure label Sep 16, 2018
@kertal kertal mentioned this issue Jan 15, 2020
Merged
27 tasks
@flash1293
Copy link
Contributor

The behavior is expected, but the message was wrong indeed. In the most recent version, the message has been fixed:
Screenshot 2021-03-11 at 12 04 22

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature:Visualizations Generic visualization features (in case no more specific feature label is available) Team:Visualizations Visualization editors, elastic-charts and infrastructure triage_needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@timroes @cjcenizal @flash1293 @Bargs @PadreZippo