Bug 1126792 - Artificial field width limit makes run's test-case entries occupy multiple lines
Summary: Artificial field width limit makes run's test-case entries occupy multiple lines
Keywords:
Status: NEW
Alias: None
Product: TCMS
Classification: Other
Component: Web UI
Version: 3.0
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: ---
: ---
Assignee: Yang Ren
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-05 09:49 UTC by Arjun Shankar
Modified: 2018-07-04 21:42 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Arjun Shankar 2014-08-05 09:49:48 UTC
Description of problem:

It appears that the width of some of the fields on the TCMS run page are limited artificially. Specifically, 'Tester' and probably also 'Assignee' fields.

Have a look at: https://tcms.engineering.redhat.com/run/165173/

The 'Tester' field's width is set so so small that it causes each row to occupy three lines of text on my rather large widescreen display, despite there being enough space to display it on one line. All the free space is occupied by the 'Summary' field instead.

Ideally, it would be nice to have the fields 'float' without artificial limits on the field size. i.e. When 'Summary' is too wide for some cases, widen the 'Summary' field. When 'Assignee' is too wide, widen that, etc.

However, if it is necessary to set an artificial limit on the field widths because of how the UI is designed right now, then I'd rather have the 'Summary' field wrap around for a *few* test cases than have the 'Tester' field wrapped into three lines for every test case.

Version-Release number of selected component (if applicable):
Nitrate 3.8.8 (our TCMS instance)

How reproducible:
Look at the list of test cases for any test run that includes cases containing sufficiently long 'Tester' field values.


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