Bug 1371273

Summary: Date/time columns under Jobs screen should be widened
Product: Red Hat Satellite Reporter: Rick Dixon <rdixon>
Component: Remote ExecutionAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: 6.2.0CC: aruzicka, jcallaha, rdixon
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-18 14:33:20 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:

Description Rick Dixon 2016-08-29 18:23:10 UTC
Description of problem:

The Date/time columns while specifying a date and time for a Job to execute should be widened; the values in the drop-down box cannot be seen in Chrome and are still partially not visible in Firefox.


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

6.2.1


How reproducible:

Always


Steps to Reproduce:

1. Try to create a new Job and click the drop-down columns in the date/time boxes; the numbers in the column are obscured (to the point of being unreadable for the "day" column) in Chrome and partially so in Firefox.


Actual results:

The numbers in the column are obscured (to the point of being unreadable for the "day" column) in Chrome and partially so in Firefox.


Expected results:

The values in these columns should be fully visible in either Chrome or Firefox.

Comment 2 Adam Ruzicka 2016-11-22 13:36:46 UTC
Is this still an issue? I'm failing to reproduce the described behavior (and don't recall ever hitting that)

tfm-rubygem-foreman-tasks-0.8.2-1.fm1_13.el7.noarch
tfm-rubygem-foreman_remote_execution-1.2.1-1.fm1_13.el7.noarch

Comment 3 Adam Ruzicka 2018-06-18 14:33:20 UTC
I'm closing this BZ since the case is closed, there was no response for almost two years and I couldn't reproduce the issue.