-
Bug
-
Resolution: Done-Errata
-
Normal
-
6.11.2
-
1
-
False
-
Sprint 133, Sprint 134, Sprint 135, Sprint 136, Sprint 137, Sprint 138, Sprint 139, Sprint 140, Sprint 141, Sprint 142, Sprint 143, Sprint 144, Sprint 145, Sprint 146, Sprint 147, Phoenix Sprint 148, Phoenix Sprint 149, Phoenix Sprint 150, Phoenix Sprint 151, Proton Sprint 2
-
sat-proton
-
None
-
None
-
None
-
Automated
Description of problem:
1. Proposed title of this feature request
To rename the “Sync Inventory Status” button to “Sync All Inventory Status” and Org level “Restart" button to “Sync Inventory” for clear understanding.
2. What is the nature and description of the request?
UI Improvement
3. Why does the customer need this? (List the business requirements here)
Current Behavior
A) Let's assume right now the satellite has two organizations ACME and TEST.
B) If we are under the context of Any Organization then,
- If we go to Configure → Inventory Upload Page we will see two Organization
ACME and TEST.
- Above right side, one option will be present Sync Inventory Status
- And if we expand ACME and TEST We have the option to Restart
C) Now if you want to upload inventory of both organizations then You have to
Click on Sync Inventory Status
D) And If you want to Sync ACME Organization inventory you have to click restart
Expectations:
- If Sync Inventory Status is performing sync on all the organizations present
on satellite then the user should be able to identify with the Button name.
Hence the request to rename it as “Sync All Inventory Status”.
- If the restart button basically does the same thing for one organization, It
should be renamed as “Sync Inventory”.
4. How would the customer like to achieve this? (List the functional
requirements here)
Simply from Satellite UI → Configure → Inventory Upload page
5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
By verifying the name of both buttons and their functions.
6. Is there already an existing RFE upstream or in Red Hat Bugzilla?
No
7. Does the customer have any specific timeline dependencies and which release would they like to target?
As soon as possible
8. Is the sales team involved in this request and do they have any additional input?
No
9. List any affected packages or components.
foreman
10. Would the customer be able to assist in testing this functionality if implemented?
Yes
- external trackers
- links to
-
RHBA-2025:155337
Important: Satellite 6.18.0 new version release
- mentioned on