User Tools

  • Logged in as: anonymous (anonymous)
  • Log Out

Site Tools


mantisbt:importexport

This is an old revision of the document!


Import Export for a list of bugs

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 an internal reference to instance A.

This includes:

Project IDs

Issue

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

Proposed solution

import will happen on a single project in instance B, so warn the user on export if “All project” is selected

User IDs

Issue

user ids will not match between the instances

Proposed solution

On import page, ask what to do with users. Options are:

  • squash all ids to a single one in instance B
  • attempt to find a matching user by username, then fallback to squashing id

Action Items

Implementation Log

* not started

Other Changes

mantisbt/importexport.1204400964.txt.gz · Last modified: 2008/10/29 04:32 (external edit)

Driven by DokuWiki