opened 09:02PM - 01 Nov 21 UTC
<!--
We use GitHub only for bug reports 🐛
Anything else should be posted t… o http://discuss.redash.io 👫
🚨For support, help & questions use http://discuss.redash.io/c/support
💡For feature requests & ideas use http://discuss.redash.io/c/feature-requests
**Found a security vulnerability?** Please email security@redash.io to report any security vulnerabilities. We will acknowledge receipt of your vulnerability and strive to send you regular updates about our progress. If you're curious about the status of your disclosure please feel free to email us again. If you want to encrypt your disclosure email, you can use this PGP key.
-->
### Issue Summary
For Chart Type Box, the Data Labels {{ column_name }} entry does not work as expected.
### Steps to Reproduce
1. Load a dataset with outliers and a Name column. In my example the dataset are the outputs of a couple functions with inputs 0 through 9, and the names are randomly generated.
2. Visualize using Visualization Type Chart, Chart Type Box, enter the numeric column under Y Columns, and under the Data Labels field put {{ Name }} as instructed in the question mark hovertext.
The name which shows up on the hovertext for any outlier appears to always come from the last row associated to the boxplot data. In this case, the last row is labeled with the name Erik, so although that is not an outlier for either boxplot, every outlier is labeled Erik.
### Technical details:
* Redash Version: Version: 8.0.0+b32245 (a16f551e)
* Browser/OS: google chrome Version 95.0.4638.54 (Official Build) (x86_64)
* How did you install Redash: V8 self hosted from Redash official cloud images
Sorry if it’s bad etiquette to zombify a Github issue here, but it’s radio silence on Github, so… could someone help figure out this labeling issue with boxplot outliers? I imagine it affects all boxplots.
jesse
November 23, 2021, 5:02am
2
Not bad etiquette at all. Thanks for drawing attention this.
It’s an outstanding issue that is not currently a priority for the core team. We are always happy to review and merge fixes from the community, however.