97197 - Say what bug you're changing product for.

Status: RESOLVED WORKSFORME

(Bugzilla :: Creating/Changing Bugs, enhancement, P3)

Description

[Matthew Tuck [:CodeMachine]]

When you get the intermediate page on product change that makes you specify new
product specific fields, it should specify which bug it is dealing with, number
and summary.

I'm moving multiple bugs at once and its easy to lose track of which bug is
which, so I can't choose the correct component.

Comment 1

[Jacob Steenhagen]

Attachment: patch (also fixes bug 94300)

Comment 2

[Jacob Steenhagen]

This patch is currently on landfill (see URL field).

Comment 3

[Gervase Markham [:gerv]]

The bug number should be somewhere on this page as well.

Gerv

Comment 4

[Matthew Tuck [:CodeMachine]]

I agree ... it's nice having the old values of the fields, but the bug number
wouldn't hurt.

Comment 5

[Jacob Steenhagen]

Attachment: patch v2

Comment 6

[Jacob Steenhagen]

Comment on attachment 47965 [details] [diff] [review]
patch (also fixes bug 94300)

Patch v2 (attachment 49026 [details] [diff] [review]) puts the bug number in the page title and header.

Comment 7

[Matthew Tuck [:CodeMachine]]

Jake it would be really nice if you could put this in a table.  Something like:

Bug XXX: Summary

Version Component Milestone
...     ...       ...

      Old Values
X       Y         Z

Comment 8

[Myk Melez [:myk] [@mykmelez]]

Comment on attachment 49026 [details] [diff] [review]
patch v2

>-print "Content-type: text/html\n\n";
>-
>-PutHeader ("Bug processed");
>-
> GetVersionTable();
> 
> if ( Param("strictvaluechecks") ) {

If strict value checks are in place, this script uses CheckFormFieldDefined
to verify that product, version, and component values have all been submitted,
but that function assumes a Content-Type header and HTML header have already
been printed.  Removing the Content-Type print statement and PutHeader function
call from before the CheckFormFieldDefined calls will thus cause an HTTP header 
corruption error.

Comment 9

[Dave Miller [:justdave]]

Jake, any chance of an update to this?  Was going to push it off, but it looks
close, so if you're going to finish it I'll leave it in 2.16

Comment 10

[Dave Miller [:justdave]]

no patch, no response, this is now 2.18

Comment 11

[Dave Miller [:justdave]]

reassigning to default owner/QA... Jake's Army Reserve unit has been deployed.

Comment 12

[Dave Miller [:justdave]]

enhancements without current patches are being pushed to 2.20

Comment 13

[Dave Miller [:justdave]]

Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004.  Anything flagged
enhancement that hasn't already landed is being pushed out.  If this bug is
otherwise ready to land, we'll handle it on a case-by-case basis, please set the
blocking2.20 flag to '?' if you think it qualifies.

Comment 14

[Jan Pieter Kunst]

I don't get it. Can I edit this? Why?

Comment 15

[Frédéric Buclin]

The trunk is now frozen to prepare Bugzilla 2.22. Only bug fixes are accepted, no enhancement bugs. As this bug has a pretty low activity (especially from the assignee), it's retargetted to ---. If you want to work on it and you think you can have it fixed for 2.24, please retarget it accordingly (to 2.24).

Comment 16

[u430950]

Bug number and summary are shown on the product change page via the 'Cancel and Return to' link.