Bug 164938 - 'Remember Search' broken when 'Name Specified' has '+' chars
Summary: 'Remember Search' broken when 'Name Specified' has '+' chars
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 3.2
Hardware: All
OS: Linux
high
medium
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-08-02 21:50 UTC by Satish Balay
Modified: 2025-10-16 23:09 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-09-16 17:14:12 UTC
Embargoed:


Attachments (Terms of Use)

Description Satish Balay 2005-08-02 21:50:38 UTC
Description of problem:

After performing a search in bugzilla - an option pops up to 'remember search'.
If the name specified [at this point] for the search has '+' chars - then this
search is unusable

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


How reproducible:

always

Steps to Reproduce:
1. do a query in bugzilla
2. 'remember the search' with the name 'stdc++_shared'
3. Now from the 'preset' queries - click on 'stdc++_shared'
  
Actual results:
I get the error:
>>
 The search named stdc _shared does not exist.
<<
Expected results:

Search to work.

Additional info:

Now I can't delete this preset search-tag anymore. When I attempt
to do that - I get:
>>
 Alternatively, you can forget  this saved search: 'stdc _shared'.
<<

But When I click that option - I see:
>>
Search is gone
OK, the stdc _shared search is gone
<<

But 'stdc++_shared' is still listed in 'Preset Queries'

Comment 1 David Lawrence 2005-08-23 19:08:35 UTC
Verified this is broken. Taking ownership.

Comment 2 David Lawrence 2008-09-16 16:53:07 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.

Comment 3 Satish Balay 2008-09-16 17:04:57 UTC
I just tried this - the new code appears to work as expected.

So this issue can be closed now.

thanks,
Satish

Comment 4 David Lawrence 2008-09-16 17:14:12 UTC
Thanks for verifying this is fixed. Closing.
Dave


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