Project

General

Profile

Actions

Bug #30221

closed

Task progress API value only needs two decimal points.

Added by Ian Ballou almost 4 years ago. Updated about 3 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

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.


Related issues 1 (0 open1 closed)

Is duplicate of foreman-tasks - Bug #30210: Task progress decimal precision discrepancy between UI, CLI, and APIClosedIan BallouActions
Actions #1

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.

Actions #2

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 #3

Updated by Adam Ruzicka about 3 years ago

  • Status changed from New to Duplicate
Actions

Also available in: Atom PDF