Bug 186381

Summary:	Boolean charts are not stored
Product:	[Community] Bugzilla	Reporter:	Juergen Bullinger <juergen.bullinger>
Component:	Bugzilla General	Assignee:	PnT DevOps Devs <hss-ied-bugs>
Status:	CLOSED WORKSFORME	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.2	Keywords:	FutureFeature
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-10-28 04:02:26 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 Juergen Bullinger 2006-03-23 09:28:57 UTC

Description of problem:
The boolean charts (i guess this is what you call it) are not saved if one
selects "and remember these as my default search options". It would really be
great if they would be saved.
In my case something strange happened, when I tried to enter a bug report.
Unfortunately this bug report was copied tens of times due to this problem. Now
if I want to see my bug reports to check if there are new infos or if I more
info is needed I have to browse a list which is almost not handelable anymore,
so I started to use this boolean charts to filter out this dupicates, but they
are lost each time.

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

How reproducible:
always

Steps to Reproduce:
1.start search
2.enter a boolean chart
3.start the search again (maybe after logging out)
  
Actual results:
the advanced search options (boolean charts) are lost

Expected results:
they should also be saved

Additional info:

Comment 1 David Lawrence 2008-09-16 16:54:19 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.