Bug 155935

Summary:	Changing columns on buglist.cgi gets browser stuck on 'Stand by' page
Product:	[Community] Bugzilla	Reporter:	David Lutterkort <lutter>
Component:	Bugzilla General	Assignee:	PnT DevOps Devs <hss-ied-bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.2	CC:	hbrock
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-11-07 16:19:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description David Lutterkort 2005-04-25 21:22:17 UTC

Description of problem:
Changing columns for a buglist gets browser stuck on 'Please stand by...' page.
In addition, browser is now stuck for any query 

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


How reproducible:


Steps to Reproduce:
1. Search for bugs
2. On resulting bug list, click on 'Change columns'
3. Add in columns 'Orig. Est.' and '% complete' and click on 'Change columns'

  
Actual results:

Browser gets stuck on 'Pondering your query/stand by' page indefinitely;
additionally, any subsequent request to buglist.cgi gets stuck in a similar way.

Expected results:

A list of bugs with the additional columns

Additional info:
This happened for me both in galeon 1.3.12 and firefox 0.8 on an up2date RHEL3
machine.

Deleting the COLUMNLIST cookie lets me at least look at buglists again, without
the time estimates though.

Is there another way to look at the time estimation information in a list ?

Comment 1 David Lutterkort 2005-04-25 21:24:28 UTC

It seems that selecting '% Completion' is the culprit - if I only add in 'Orig.
Est.' and 'hours left' things seem to work.

Comment 2 David Lawrence 2005-04-25 21:28:35 UTC

Will look into this. Thanks for the report.

Comment 3 David Lawrence 2008-09-16 16:52:28 UTC

Red Hat Bugzilla is now using version 3.2 of the Bugzilla codebase and therefore this bug will need to be re-verified against the new release. With the updated code this bug may no longer be relevant or may have been fixed in the new code.
Updating bug version to 3.2.