Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 162762 - Changes made before logging in cause error
Summary: Changes made before logging in cause error
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 3.2
Hardware: All
OS: Linux
medium vote
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2005-07-08 13:33 UTC by Andrew Overholt
Modified: 2013-06-24 02:54 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-10-02 18:03:03 UTC

Attachments (Terms of Use)

Description Andrew Overholt 2005-07-08 13:33:07 UTC
Description of problem:
If I enter changes to a bug and hit 'commit' or 'save changes' while not logged
in, bugzilla correctly prompts me to log in but then throws an error after I
enter my username and password.  Entering the same information _after_ logging
in results in correct operation.

Version-Release number of selected component (if applicable):
it says "Bugzilla Version 2.18" in the bottom left corner

How reproducible:

Steps to Reproduce:
1. Go to a bug report while not logged in (say, from a link in an email)
2. Make changes to the bug (that you are allowed to do)
3. Hit commit/save and enter login information when prompted
Actual results:
"Form field target_milestone was not defined; this may indicate a bug in your

Expected results:
Bug updates proceed as expected.

Additional info:

Comment 1 David Lawrence 2006-04-08 17:42:25 UTC
Red Hat's current Bugzilla version is 2.18. I am moving all older open bugs to
this version. Any bugs against the older versions will need to be verified that
they are still bugs. This will help me also to sort them better.

Comment 2 David Lawrence 2008-09-16 16:52:58 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 Andrew Overholt 2008-10-02 18:03:03 UTC
I don't think this is still present.

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