Closed Bug 262182 Opened 20 years ago Closed 20 years ago

editing a buglist from a tabular report goes to wrong page

Categories

(Bugzilla :: Query/Bug List, defect)

2.18
defect
Not set
normal

Tracking

()

RESOLVED FIXED
Bugzilla 2.18

People

(Reporter: robzilla, Assigned: gerv)

References

()

Details

Attachments

(1 file, 1 obsolete file)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.1) Gecko/20040707
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.1) Gecko/20040707

When you run a tabular report, and then click on one of the numbers in a table
to get a bug list, and then click on the "Edit search" link at the bottom of that
bug list, it takes you back to the "Generate Tabular Report" page, instead of
the query page.

Reproducible: Always
Steps to Reproduce:





I used the following to fix this problem (sorry, my installation is too
customized to give a usable patch)
       
      [% editqueryurl = urlquerypart FILTER html;
         editqueryurl = editqueryurl.replace('&?query_format=.*?(&|$)','&');
         editqueryurl = editqueryurl.replace('&+', '&');
         editqueryurl = editqueryurl.replace('(^&)|(&$)', '');
      %]
...
     <a href="query.cgi?[% editqueryurl %]......
Version: unspecified → 2.18
Status: UNCONFIRMED → NEW
Ever confirmed: true
Attached patch Patch v1 (obsolete) — Splinter Review
I think any solution to this problem would be a hack, but this is probably the
better hack.  In buglist.cgi, simply remove "query_format=report-table" from
$::buffer, and it's all good.
Assignee: justdave → rsiklos
Status: NEW → ASSIGNED
Attachment #161186 - Flags: review?
Flags: blocking2.20?
Flags: blocking2.18?
OS: Windows XP → All
Hardware: PC → All
Attachment #161186 - Flags: review? → review?(gerv)
Flags: blocking2.20?
Flags: blocking2.20-
Flags: blocking2.18?
Flags: blocking2.18-
Whiteboard: will accept for 2.18 branch, not blocking release though.
Target Milestone: --- → Bugzilla 2.18
Attached patch Patch v.2Splinter Review
Actually, this is the correct fix - to not put it in there in the first place
:-) 

Rob: thanks for your bug report(s), and your patch(es). Would you be able to
review this for my by verifying that if you remove your hack, and add mine, it
still fixes the problem for you?

Gerv
Assignee: rsiklos → gerv
Attachment #161186 - Attachment is obsolete: true
Attachment #161186 - Flags: review?(gerv) → review-
Attachment #163251 - Flags: review?(rsiklos)
Comment on attachment 163251 [details] [diff] [review]
Patch v.2

looks good to me Gerv.	Thanks!
Attachment #163251 - Flags: review?(rsiklos) → review+
Flags: approval?
Flags: approval2.18?
Flags: approval?
Flags: approval2.18?
Flags: approval2.18+
Flags: approval+
Checking in report.cgi;
/cvsroot/mozilla/webtools/bugzilla/report.cgi,v  <--  report.cgi
new revision: 1.27; previous revision: 1.26
done

Checking in report.cgi;
/cvsroot/mozilla/webtools/bugzilla/report.cgi,v  <--  report.cgi
new revision: 1.24.2.2; previous revision: 1.24.2.1
done
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Whiteboard: will accept for 2.18 branch, not blocking release though.
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: