User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 When the list of priorities is modified in localconfig, and a bug is imported with an unsupported priority, then the priority 'P3' is assigned in importxml.pl (line 419). This results in a bug with an invalid priority. Reproducible: Always Steps to Reproduce: 1. Install a fresh copy of bugzilla 2. Modify the list of priorities in localconfig (and run checksetup) 3. import a bug with an invalid priority Actual Results: sanity check produces a red line like: Bug(s) found with invalid priority value Expected Results: importxml should not insert a bug with invalid priority.
*** Bug 198569 has been marked as a duplicate of this bug. ***
Probably what it needs to do is look up the default priority and use that instead.
I cannot reproduce in 2.19.1. I have just imported 300 bugs from an XML file I generated externally which had a <priority> tag in the XML for each bug, and each was imported with its correct priority.
This is only the case if the priority that comes over from the move.pl is not in the list of priorities for the importing installation. I have changed it to use the defaultpriority parameter instead of the P3.
fixed by bug 285614