Bug 2179974

Summary: [RFE] Mandatory fields can mark with astarix charactor (ex- * )
Product: Red Hat Satellite Reporter: visawant
Component: SCAP PluginAssignee: Oleh Fedorenko <ofedoren>
Status: CLOSED ERRATA QA Contact: Peter Ondrejka <pondrejk>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.13.0CC: aruzicka, mhulan, rlavi, shwsingh, zhunting
Target Milestone: 6.15.0Keywords: FutureFeature
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-foreman_openscap-7.1.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-04-23 17:13:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Name field without astarix character none

Description visawant 2023-03-20 13:11:37 UTC
Created attachment 1952065 [details]
Name field without astarix character

Description of problem: Mandatory fields are not marked with asterisk character, which leads to confusion about whether a random name will be used or not on the Compliance Policies page.


Version-Release number of selected component (if applicable): 6.13.0 Snap 15


How reproducible: Always


Steps to Reproduce:
1. Go to Hosts > Policies page
2. Click on "New Compliance Policy" button, go to the Policy Attributes section
3. without entering Name , Description click Next button.

Actual results: Error message will be appear, which is expected. But we can have * charactor in front of Name field


Expected results: Expect * charactor in front of Name field


Additional info: Attached screenshot for the same

Comment 2 Oleh Fedorenko 2023-09-04 15:58:47 UTC
Created redmine issue https://projects.theforeman.org/issues/36718 from this bug

Comment 3 Bryan Kearney 2023-09-04 16:02:46 UTC
Upstream bug assigned to ofedoren

Comment 4 Bryan Kearney 2023-09-04 16:02:48 UTC
Upstream bug assigned to ofedoren

Comment 5 Bryan Kearney 2023-10-05 16:02:21 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36718 has been resolved.

Comment 10 errata-xmlrpc 2024-04-23 17:13:56 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.15.0 release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2024:2010