Closed
Bug 190049
Opened 22 years ago
Closed 19 years ago
importxml.pl should not allow DUPLICATE bugs to be imported
Categories
(Bugzilla :: Bug Import/Export & Moving, defect)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.22
People
(Reporter: justdave, Assigned: gregaryh)
References
Details
(Whiteboard: [blocker will fix])
importing a bug from another installation which was RESOLVED DUPLICATE on the original installation causes referential integrity problems when it's imported, since the bug it's duped to (which is stored now) will not exist in the target database. RESOLVED DUPLICATE should either be rejected, or changed to RESOLVED INVALID when the bug is written to the new database.
Reporter | ||
Updated•21 years ago
|
Component: Administration → Bug Import/Export & Moving
Comment 1•20 years ago
|
||
Is the ID of the duplicate bug one of the fields that is imported? If so, the statement in the manual that the import XML syntax is the same as that shown from ctype=xml query against a bug is incorrect as the XML shown in that scenario does not include the ID of the duplicate bug.
Updated•19 years ago
|
Assignee: nobody → ghendricks
Assignee | ||
Updated•19 years ago
|
Status: NEW → ASSIGNED
Comment 2•19 years ago
|
||
imported bugs having the DUPLICATE resolution are changed to MOVED. The maintainer can then triage them easily. This is fixed by bug 285614.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Whiteboard: [blocker will fix]
Target Milestone: --- → Bugzilla 2.22
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•