mantisbt:importexport
This is an old revision of the document!
Table of Contents
Import Export for a list of bugs
- Author: Gianluca Sforna (giallu)
- Status: Draft |
Work in Progress|Implemented - Associated Issue: http://www.mantisbt.org/bugs/view.php?id=4220
Introduction
A complete solution for copying a list of issues between two different Mantis instances is something asked from quite some time:
http://www.mantisbt.org/bugs/view.php?id=4220
For a greater flexibility, the use of an XML format looks like the best option (XML export was also asked in http://www.mantisbt.org/bugs/view.php?id=4024)
Implementation Notes
We assume a Mantis instance (A) as the source, and another instance (B) as the destination. A possible workflow could be:
- Select a set of issues in A using filters
- Activate the Export command
- An XML file is produced and downloaded
- Log in instance B as administrator
- Import the XML file and watch instance B populated with new bugs
Design choices and issues
The main hurdle for this feature is to define the behavior when any piece of information is a internal reference to instance A.
This includes:
- Projects - the selected issues could be from more than one project in instance A and there is no guarantee the same project(s) will be in instance B
- assume the import will be in a single project, so warn the user on export
- User IDs
Action Items
Implementation Log
* not started
Other Changes
mantisbt/importexport.1204382769.txt.gz · Last modified: 2008/10/29 04:31 (external edit)