Actions
Bug #30221
closedTask progress API value only needs two decimal points.
Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Description
I'm working on this bug (https://projects.theforeman.org/issues/30210?issue_count=17&issue_position=1&next_issue_id=30112) and the proposed solution is to remove the decimals from the UI task progress and have only an integer percentage. As a result, we will only need two points of precision from the ForemanTasks API task progress value.
Updated by Ian Ballou almost 4 years ago
I will probably end up addressing this in the PR that addresses https://projects.theforeman.org/issues/30210?issue_count=17&issue_position=1&next_issue_id=30112, so I think this could be marked as duplicate.
Updated by Adam Ruzicka about 3 years ago
- Is duplicate of Bug #30210: Task progress decimal precision discrepancy between UI, CLI, and API added
Actions