View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0004987||mantisbt||customization||public||2004-12-15 12:17||2019-12-13 18:06|
|Status||closed||Resolution||no change required|
|Summary||0004987: Added export functionality into other Mantis instance|
We use Mantis as our helpdesk system on a few locations, all separate installations. In some cases an issue should be moved form one installation to another, ie from one database to the other.
If people are interested, let me know and i will create a small distro.
Required setting(s) within config_inc.php :
|Tags||No tags attached.|
Sounds interesting. I can venture a guess, but could you explain how it works?
The table will hold information on the various Mantis instances, including information on Category & project to move incoming issues into.
maintenance of the table is only allowed for Administrators. There is an option available to verify the connection to the other instance.
Hopefully the above makes sense ?
But how does it export?
It connects to the remote db and adds the issue there using, for now, direct sql statement into bug_table, bug_history_table,bug_text_table.
It would be nice if you could do this with some sort of RPC, so you don't need direct access to the database (and nothing messes up if you have different versions).
Not sure if I agree, with your suggestion, i could even add to other instances without them having these scripts, versions are hardly an issue since I am exporting essentials only.
Well, the scripts would be added to the distribution, so any Mantis released after the scripts have been included should be usable.
The advantage of this approach is that you won't mess anything up if the database structure changes, nor will you need direct access to the other MySQL server.
Point taken, will try to add rpc mode.
MantisConnect is a webservice developed in PHP and runs on top of Mantis. It can be used to submit an issue to a remote Mantis installation. It can also be used to submit notes. Attachments are partially supported, and history is not supported yet.
MantisConnect also allows retrieving the projects and categories within these projects.
See http://www.futureware.biz/mantisconnect for more details. A lot of the above features are part of the next version of MantisConnect which is expected to release with Mantis 1.0.0a3.
Following are issues with copying or moving issues from one Mantis instance to another:
First impression is that this would not fit my purpose plus it means a lot of work to get it set up. I also do not like the dependancy on dot.net but that is a personal view. I want to be able to use a mashed network of Mantis installations which my dev does. It is fairly basic and that's why i hoped it would become an integral part of Mantis opposite a seperate development. Jeroen's suggestion to avoid direct access to the database is omething which i subscribe but I have not been able to really work on that, any suggestions are welcome.
If i understand correctly, this is not on the list to become part of Mantis so I will have to keep my code up to date so it keeps on working with future versions of Mantis.
I will make the updated code available through my website at www.nuy.info
Would be cool if you make this available as a Mantis plugin using the 1.2.0 plugin support feature.
I've implemented the same feature sometime ago. I did this via MantisConnect (which is a PHP webservice, hence, no dependency on .NET). The idea is that the Mantis instances could be hosted on totally different servers. This code is packaged with MantisConnect as an example of consuming the webservice from a PHP client.
Well, I am working on this plugin so it will become available again.
I believe this is mostly obsolete, and would nowadays be done via REST API or similar. Not sure if there was ever a Mantis plugin released, if so it should be added to mantisbt-plugins org on GitHub.
As a consequence, I'm closing this issue, but feel free to reopen if you believe it is still applicable and worth keeping in this tracker as something to include in Mantis.
|2004-12-15 12:17||CasNuy||New Issue|
|2004-12-16 08:41||jlatour||Relationship added||child of 0004937|
|2004-12-16 08:42||jlatour||Note Added: 0008657|
|2004-12-16 08:42||jlatour||Status||new => feedback|
|2004-12-16 11:35||CasNuy||Note Added: 0008664|
|2004-12-16 11:59||jlatour||Note Added: 0008665|
|2004-12-16 17:15||CasNuy||Note Added: 0008677|
|2004-12-16 17:25||jlatour||Note Added: 0008678|
|2004-12-17 14:23||CasNuy||Note Added: 0008707|
|2004-12-17 14:51||jlatour||Note Added: 0008710|
|2004-12-17 15:11||CasNuy||Note Added: 0008712|
|2005-05-18 09:36||vboctor||Note Added: 0010166|
|2005-05-22 06:20||CasNuy||Note Added: 0010190|
|2008-07-13 15:48||vboctor||Note Added: 0018463|
|2008-07-14 16:43||cas||Note Added: 0018515|
|2008-07-15 02:50||cas||Note Edited: 0018515|
|2019-12-03 09:50||dregad||Assigned To||=> dregad|
|2019-12-03 09:50||dregad||Status||feedback => resolved|
|2019-12-03 09:50||dregad||Resolution||open => no change required|
|2019-12-03 09:50||dregad||Note Added: 0063177|
|2019-12-13 18:06||atrol||Status||resolved => closed|