Closed
Bug 329730
Opened 20 years ago
Closed 20 years ago
After implementing classifications, when entering a bug the owner and qa contact aren't prefilled
Categories
(Bugzilla :: Creating/Changing Bugs, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: sue.salamacha, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910
Build Identifier: Bugzilla 2.20.1
Updated a 2.18 installation to 2.20.1 and implemented the classifications. Now when entering a new bug for a product the owner and qacontact fields (that used to be prefilled) are blank. As the user drop down has been selected, that list is available. I noticed that if there is only 1 component in the product the owner and qacontact ARE filled in but for any more than 1 component they aren't.
Reproducible: Always
Steps to Reproduce:
1. Select enter bug
2. Select the classification
3. Select product
4. Owner and QAcontact fields are not pre-filled
Actual Results:
If there is only 1 component in the product the owner and qacontact fields are filled with those values specified for the component. If there is more than 1 component in the product then those fields are blank.
Expected Results:
I expected the fields to have the default owner and qacontact for the component filled in as has been the case since release 2.18
We have some mod to our installation of bugzilla but to ascertain that we had not contributed to the situation, I installed a vanilla 2.20.1 release on a test system and use a dump of our database and the result was the same as reported.
two silly questions:
1. your browser has js enabled?
2. if you file a bug w/ those fields blank, does the resulting bug have the values filled in properly?
(no, neither of these questions make up for the problem you see, i'm just curious.)
| Reporter | ||
Comment 2•20 years ago
|
||
Thanks for being curious - continuing to file the bug resolved the fields so I'll mark this as invalid.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•