0007970: Synchronization between different Mantis Instances - MantisBT - Signup temporarily disabled due to spam

ID	Project	Category	View Status	Date Submitted	Last Update

0007970	mantisbt	other	public	2007-05-15 02:57	2014-06-04 02:34

Reporter	Martin Fuchs	Assigned To
Priority	normal	Severity	feature	Reproducibility	have not tried
Status	new	Resolution	open

Summary	0007970: Synchronization between different Mantis Instances
Description	There has been a recent discussion on the mailing list about synchronization between different mantis instances and "bug replication". There seem to be are a few home brewn tools to full fill the main requirements, but there is still missing a generalized solution. I have also written some utilities for our special environment, but it's implemented in C++ and Java, as I am not a PHP programmer. It's also using a Web service, but independent from MantisConnect. I guess you are not willing to take my code as starting point. ;-) So let's start with the design phase and write down the requirements and useful features in an associated Wiki page.
Tags	No tags attached.

sirshurf 2007-05-15 03:06 reporter ~0014535	That is something I have thought about... especially if I will be aible to split the program with see permitions (Not allways I would like, for one user to see that a close bug exits in another users program)

Martin Fuchs 2007-05-15 03:42 reporter ~0014536	In the meanwhile, while waiting for access to the Wiki page, here is my first proposal of an requirement description: A common setup is the installation of one Mantis instance (let's call it "extern") with customer access and another instance with access for developers also containing some entries hidden from the customer (let's call it "intern"), may be also containing notes generated by CVS/SVN commits. The entries of this two Mantis instances should be synchronized. The relationship between the two instances is a master/slave relation: The external instance can be used to enter new issues from the outer side. This should become immediately visible in the internal instance. But the master for the entry status is located in the internal instance. (May it would be useful to be able to configure a master detail chain with more than two instances.) It should be possible to host the two instances on two different machines to separate internal and external networks. The configuration of replication features should be on a project base, so it's possible for example to activate synchronization only for part of the existing projects. There should be the possibility to configure a mapping for different attributes between the two instances like category, assignees and may be status. The following things should be synchronized automatically: . new entries from slave to master . newly attached notes from slave to master . status changes from master to slave There should be an user interface to synchronize entries in both directions. There should be an overview page showing the list of related entries of both instances side by side. Filtering functionality at least for the status is very useful in this list, for example to get an quick overview of open issues. The connection between entries of the two instances can be implemented by using user defined fields: . In the external instance there are stored the IDs of internal entries. . In the internal instance there are stored the URLs to immediately get to the external entries. (This is our current implementation without any need to change the Mantis code. Of course it would be possible for example only to store the IDs of the other instance in any of the two instances and generate the URLs on the fly in the Mantis PHP code.) Well, that are my ideas for now. The Wiki page should be more appropriate to add more descriptions and edit the existing ones.