Bug 86294 – "edit this query" doesn't work after selecting a preset query

Bug 86294 - "edit this query" doesn't work after selecting a preset query

Summary:	"edit this query" doesn't work after selecting a preset query

Status:	CLOSED WORKSFORME

Aliases:	None

Product:	Bugzilla
Classification:	Community
Component:	Bugzilla General (Show other bugs)
Sub Component:
Version:	2.17
Hardware:	All Linux

Priority	medium Severity medium (vote)
Target Milestone:	---
Target Release:	---
Assigned To:	David Lawrence
QA Contact:	David Lawrence
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-03-18 22:05 EST by Roland McGrath
Modified:	2007-04-18 12:52 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2003-03-27 16:28:14 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Roland McGrath 2003-03-18 22:05:11 EST

Description of problem:

After selecting a preset query, "edit this query" leads to a blank form,
not one with the preset query's details filled in.

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

The little black line says 2.17.1.

How reproducible:

100%

Steps to Reproduce:
1. Have stored a preset query before.
2. Click on one of your "Preset Queries" footer links.
3. Click on "Edit this query".
    
Actual results:

Empty query form.

Expected results:

Prefilled query form matching the preset query.

Additional info:

This makes me sad.  I want bugzilla to make me happy.

Comment 1 Mike McLean 2003-03-26 20:21:12 EST

I think this might be a dup of bug#86130

Comment 2 Roland McGrath 2003-03-27 16:28:14 EST

That (86130) might have been the failure mode, I don't recall.
However, the problem no longer happens for me.  It now works right.

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