Bug 1371273 - Date/time columns under Jobs screen should be widened
Summary: Date/time columns under Jobs screen should be widened
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.2.0
Hardware: x86_64
OS: Linux
low
medium vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-29 18:23 UTC by Rick Dixon
Modified: 2020-04-02 14:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-18 14:33:20 UTC
Target Upstream Version:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.