Bug 1326643 - Product and Component field got truncated when the strings are very long
Summary: Product and Component field got truncated when the strings are very long
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: User Interface
Version: 5.0
Hardware: Unspecified
OS: Unspecified
low
low vote
Target Milestone: 5.0
Assignee: Jeff Fearn 🐞
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-13 09:27 UTC by Hui Wang
Modified: 2018-12-09 06:29 UTC (History)
4 users (show)

Fixed In Version: rh-bugzilla-5.0.3-rh2.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-06 07:50:01 UTC

Attachments (Terms of Use)
Userpref (15.26 KB, image/png)
2016-04-13 09:27 UTC, Hui Wang 		no flags Details
component (4.01 KB, image/png)
2016-04-13 09:30 UTC, Hui Wang 		no flags Details
product (3.86 KB, image/png)
2016-04-13 09:30 UTC, Hui Wang 		no flags Details
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Description Hui Wang 2016-04-13 09:27:40 UTC 
Created attachment 1146771 [details]
Userpref

Description of problem:
Product and component field got truncated when the strings are very long. See also the attachment

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

How reproducible:
Always

Steps to Reproduce:
1.Create a rhel7 bug, then select component 'Red_Hat_Enterprise_Linux-Release_Notes-7-zh-TW', save
2.
3.

Actual results:
The component field value got truncated

Expected results:
not truncated, It is better show in 1 lines, but in 2 lines also acceptable.

Additional info:
check attachment
Comment 1 Hui Wang 2016-04-13 09:30:37 UTC 
Created attachment 1146773 [details]
component
Comment 2 Hui Wang 2016-04-13 09:30:58 UTC 
Created attachment 1146774 [details]
product
Comment 3 Jeff Fearn 🐞 2016-05-30 02:03:04 UTC 
Fix for BZ 1320095 fixed this.
Comment 4 Hui Wang 2016-05-31 08:31:10 UTC 
Verified the issue.
The result is PASS
version 5.0.3.rh1
Note You need to log in before you can comment on or make changes to this bug.