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

Bar chart with second y axis overlaps data series #2292

Closed
dncpax opened this issue Feb 5, 2018 · 14 comments · Fixed by #4150
Closed

Bar chart with second y axis overlaps data series #2292

dncpax opened this issue Feb 5, 2018 · 14 comments · Fixed by #4150

Comments

@dncpax
Copy link

dncpax commented Feb 5, 2018

Issue Summary

Discussion here: https://discuss.redash.io/t/bar-chart-with-second-y-axis-overlaps/1493/3.
In a bar chart, when choosing to display a data series on the secondary y axis to the right, the data series overlaps all others:
image

It shouldn't. The correct solution is to display all data series side-by-side regardless of y axis.
Example from google sheets:
1 y axis
image

2 y axis
image

Occurs on v3.

Steps to Reproduce

  1. Create bar chart with at least 2 data series
  2. Configure 1 data series to use a secondary y axis

Any other info e.g. Why do you consider this to be a bug? What did you expect to happen instead?
I don’t think that’s the correct behaviour a secondary y axis should have. Why would anyone want a data series to entirely cover up other data series?
The objective of a secondary y axis is to allow very different ranges of values to be plotted on the same graph.

Technical details:

  • Redash Version: 3.0
  • Browser/OS: any
  • How did you install Redash: ubuntu provision script
@chuckume
Copy link

chuckume commented Apr 3, 2018

I have exactly the same problem.

@dncpax
Copy link
Author

dncpax commented Mar 8, 2019

Just trying to get traction on this.
Really, a no-brainer and super-strange to explain people redash does not support such a common use-case.

@dncpax
Copy link
Author

dncpax commented Mar 8, 2019

Seems a plotly issue to be resolve in v1.45.0:
plotly/plotly.js#78
PR already merged: plotly/plotly.js#3529

Example here: https://codepen.io/etpinard/pen/yZQYzq?editors=1010

@dncpax
Copy link
Author

dncpax commented Mar 8, 2019

Ok, v1.45 is already out! They're on v1.45.2 already!

Any takers??

@kravets-levko
Copy link
Collaborator

Hi @dncpax! We're in the middle of React migration, and therefore have some blockers related to that. I think I'll take this after #3493 merged.

@dncpax
Copy link
Author

dncpax commented Mar 8, 2019

Hi @kravets-levko thanks for the update. Been looking forward for the many great things you guys are doing.

@tharapita
Copy link

tharapita commented Sep 18, 2019

Any updates? Does not seem to be in 7.0.0.

@puneetjindal
Copy link

@kravets-levko
I have an angular based web app and currently exploring for dashboarding solution. Having dual axis chart is kind of a MVP requirement. Its somehow difficult to locate from the above discussions whether we can build dual Y axis as per the expected behaviour or not? Please help me point towards its implementation!

@susodapop
Copy link
Contributor

I reproduced this on the preview instance here.

@kravets-levko
Copy link
Collaborator

kravets-levko commented Aug 3, 2020

@susodapop PR that fixes it (#4150) wasn't merged yet

@dncpax
Copy link
Author

dncpax commented Aug 5, 2020

Wuhu! Good news! Thanks guys!

@mmbader
Copy link

mmbader commented Nov 9, 2020

Wuhu! Good news! Thanks guys!

Sorry, just to clarify - is this implemented now? How can I enable this functionality? Thanks!

@kravets-levko
Copy link
Collaborator

@mmbader Yes, it's fixed now, you should just upgrade to latest version

@mmbader
Copy link

mmbader commented Nov 9, 2020

image

Sorry for the noob question - where can I see which version I am currently using? Is it the one at the bottom of my screenshot? (Version: 4172e048)

Thanks for your help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants