Context:
Currently, Optimize rounds bucket keys to two decimal places. This amount of decimal places for rounding should be configurable in case users require more accuracy. Additionally, the current setup can be confusing if users configure a bucket size with more than two decimal places since Optimize will round the result bucket keys, which makes it look like the incorrect bucket size was used. Attached is a screenshot that shows the issue.
We could consider adding a warning to the frontend if users configure a bucket size that has more decimal places than are configured in Optimize for bucket keys, or potentially we could think about not allowing users to set a bucket size with more than the configured decimal places.
AT:
- Users can configure how many decimal places Optimize should use for number variable report bucket keys
- We handle the case that users configure a bucket size with more than the "allowed" number of decimal places in a way that is less confusing
Hint:
Consider significant figures
This is the controller panel for Smart Panels app
- is related to
-
OPT-3492 Configure custom buckets for grouping by Number and Date Variables
-
- Done
-