Bug 1020897

Summary: Strange results when including "URL" column in results.
Product: [Community] Bugzilla Reporter: Stephen Gordon <sgordon>
Component: Query/Bug ListAssignee: Simon Green <sgreen>
Status: CLOSED CURRENTRELEASE QA Contact: tools-bugs <tools-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.4CC: ebaak, jmcdonal, rjoost
Target Milestone: 4.4Keywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.4.1012 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-06 04:40:09 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:
Attachments:
Description Flags
URL search results. none

Description Stephen Gordon 2013-10-18 13:27:56 UTC 
Created attachment 813774 [details]
URL search results.

Description of problem:

I am executing the following query to select bugs from the Red Hat OpenStack product that have the URL field set, displaying only the Bug ID and URL fields:

https://bugzilla.redhat.com/colchange.cgi?classification=Red%20Hat&columnlist=bug_file_loc&f1=bug_file_loc&list_id=1819900&o1=isnotnull&product=Red%20Hat%20OpenStack&query_format=advanced&query_based_on=

In the resultant output there are several issues:

1) Despite the entire width of the screen being available to display only 2 columns the URL field is truncated to the point that the URLs are largely indistinguishable from each others (as they are all different pages from the same domain in this case).

2) The URL is not a clickable link like it is in the bugs themselves so there is in fact no way to determine the full URL from the query view.

3) The column header for the URLs is "OS"?
Comment 1 Jason McDonald 2013-10-21 03:32:13 UTC 
I can reproduce all three of the above issues.
Comment 3 Simon Green 2013-12-06 04:40:09 UTC 
This change is now live. If there are any issues, do not reopen this bug.
Instead, you should create a new bug and reference this bug.

  -- simon