-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Static viz multi-series shows two Y-axis #20559
Comments
After some more debugging, the example is using a "series": [
{
"name": "bar series 1",
"color": "#88bf4d",
"yAxisPosition": "left",
"type": "bar",
"data": [
...
],
},
...
} In the GH issue example, it seems that the series all have |
Tested this on 1.46.1 and So Step 1 ,create the following question -> Orders -> Count -> Group by Created_at:Month and Product -> Category: Step 2, set visualization as a Line and make sure the split is disabled Step 3, Add it to dashboard and send it to an email Reopening issues |
@Tony-metabase can you help me reproduce it? I couldn't on 46.1 |
Any specific step you are getting stuck? Since same replication steps apply as the one flamber created ... So Step 1 ,create the following question: Step 2, set visualization as a Line and make sure the split is disabled Step 3, Add it to dashboard and send it to an email You get split Y-axis which are not there in the question and are also disabled form the settings ... Anything not clear let me know Happens both on 1.46.1 and |
@Tony-metabase Can Chromium or Firefox be used to replace the existing solution? |
Describe the bug
Static viz multi-series shows two Y-axis.
Kinda a regression in 0.42.0, since 0.41.6 would just show a table, but at least there wasn't a correctness issue with that.
To Reproduce
/api/pulse/preview_card_png/:question_id
Expected behavior
Follow Y-axis choices from normal visualization settings.
Information about your Metabase Installation:
Tested 0.41.6 and 0.42.0
⬇️ Please click the 👍 reaction instead of leaving a
+1
orupdate?
commentThe text was updated successfully, but these errors were encountered: