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.

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

[Bug][Lens][Dashboard] Dashboard title encoding issue after navigating back from creating new Lens vis #54723

Closed
Dosant opened this issue Jan 14, 2020 · 0 comments · Fixed by #54738
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Dashboard Dashboard related features Feature:Lens v7.6.0

Comments

@Dosant
Copy link
Contributor

Dosant commented Jan 14, 2020

Kibana version: master, 7.x, 7.6

Introduced in: #53110

Describe the bug:

After creating new Lens visualisation and navigating back to dashboard, the encoding in dashboard title (and probably other places where state is coming from URL) gets messed up

e.g.

Having dashboard title:
This is a new dashboard -> This%20is%20a%20new%20dashboard

Steps to reproduce:

  1. Create a dashboard with spaces in title
  2. Add new visualisation -> Create new -> Lens
  3. Create Lens Vis and Save it.

After automatically navigating back to dashboard the dashboard title on UI gets wrong encoding.

Expected behavior:

The title should stay the same.

Screenshots (if relevant):

Screenshot 2020-01-14 at 14 31 29

Errors in browser console (if relevant):

No

Provide logs and/or server output (if relevant):

Any additional context:

@Dosant Dosant added bug Fixes for quality problems that affect the customer experience Feature:Dashboard Dashboard related features Feature:Lens v7.6.0 labels Jan 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Dashboard Dashboard related features Feature:Lens v7.6.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants