Actions
Bug #20573
closed
Compliance of rules should not be rounded to the nearest hundredth
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Description
We should round to the nearest whole number, as we usually do.
Updated by Raphael GAUTHIER over 2 years ago
- Status changed from New to In progress
Updated by Raphael GAUTHIER over 2 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Raphael GAUTHIER to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/4110
Updated by François ARMAND about 2 years ago
- Status changed from Pending technical review to In progress
- Assignee changed from Vincent MEMBRÉ to François ARMAND
I'm taking over this issue!
Updated by François ARMAND about 2 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request changed from https://github.com/Normation/rudder/pull/4110 to https://github.com/Normation/rudder/pull/4115
Updated by François ARMAND about 2 years ago
- Related to Bug #20553: Regression on displaying small percent in compliance bar added
Updated by François ARMAND about 2 years ago
- Pull Request changed from https://github.com/Normation/rudder/pull/4115 to https://github.com/Normation/rudder/pull/4110
Finally, we will keep the UI rounding for 7.0 but allows to have precision in API in subtask.
Updated by Raphael GAUTHIER about 2 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|74557565709ea944b9023c00bfe39a8d6bd80beb.
Updated by Vincent MEMBRÉ about 2 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.0.0~rc3 which was released today.
Actions