Mantis Bug Tracker - Forums

Is it possible to configure two mantis installations to allow for distributed bug tracking? I have a copy of Mantis installed on a VM I take with me to the field and run on my laptop. Now management has seen it and wants a copy on a central server so they can track progress, but I can't always reach the internet when I'm in the field. I'd like to update my VM data, then sync up with the central server when it's available.

I read that MySQL supports asynchronous replication, and if I understood correctly, this sounds like it could do exactly what I want. Anyone else out there try this before?

Oops, forgot to mention that I'm running 1.17 on my laptop VM and 1.18 on the central server. Early stages of adaptation, though, would be easy to delete everything and start new if that would make this easier.

Ok, so far, I've figured out that this is referred to as an Occasionally Connected System. MySQL replication does support this, but the implications are that the underlying application should be built to also support the consequences of this, and I'm guessing Mantis is not. For example, what happens if two disconnected people change the status of an issue, then sync. I don't know what it does, but I'm pretty sure that whatever it is, it isn't good.