Bug 2163319

Summary: The 'Generate at' option present in Report templates when generating reports has overlapped Calender with time.
Product: Red Hat Satellite Reporter: Ayush <aymishra>
Component: ReportingAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.13.0CC: jlenz
Target Milestone: UnspecifiedKeywords: Triaged, UserExperience
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-25 12:37:15 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
Shows the issue clearly none

Description Ayush 2023-01-23 09:06:58 UTC 
Created attachment 1939923 [details]
Shows the issue clearly

Description of problem:
Refer to this bug Bug 2162637, The issue present in 2162637 is persists in all the options like Subscription-reports, Ansilbe inventory, User-registered users etc.


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

How reproducible:
always

Steps to Reproduce:
1. Navigate to Monitor -> Report template ->  Click on any option(Applied Errata, Subscription reports etc)
2. Click on "Generate" option  in the right
3. On the "Generate at" option the calender and time is overlapping. Also the time can't be changed only "AM" and "PM" can be changed

Actual results:
Calender and time options are overlapping in the "Generate at" option when generating the Errata report and Time can't be changed for the same.

Expected results:
Calender and time should not overlap

Additional info:
Comment 1 Brad Buckingham 2023-01-23 14:07:20 UTC 
Is this a regression from 6.12?  Thanks!
Comment 2 Ayush 2023-01-23 16:45:57 UTC 
No, this issue is present in 6.12.0 and 6.13.0 as well
Comment 4 Jeremy Lenz 2023-05-25 12:37:15 UTC 

*** This bug has been marked as a duplicate of bug 2162637 ***