On May 12, 10:08 am, Ice Polar <[email protected]> wrote: > Hi, > > what a platform do you have (Linux / Windows) and wich db (SQLite / MySQL). > Dependnig on that there will be different possibilities for a solution. > sincerley > Ice > > 2009/5/11 W. Martin Borgert <[email protected]> > > > > > Hi, > > > I would like to synchronize some tickets between two trac instances. > > > Background: There is one instance for the front desk and another one > > for the development department. For some reasons front desk staff > > can't be allowed to access the development trac and vice versa. > > > Extra points, if the mechanism handles attachments gracefully and > > changes links into intertrac links :~) > > > Many thanks in advance!
Just out of curiosity, is this a physical limitation (i.e, the help desk can't actually access the trac server) or some poorly thought out "shall not happen" restriction? The reason I ask, there are some plugins for CustomerSupport type tickets that limit what can be done for creating tickets. Combined with other plugins like PrivateTickets, and also modifying permissions, you could easily limit "front desk people" to only creating tickets, and only seeing their own tickets, disallowing all coded, wiki, reports, etc. pages, and not even seeing tickets created by others. Might be worth a look to see what can be done, and see if that fits within the intent of the "shall not access" edict's actual intent. Otherwise you have some messy trigger to kick off a replication and restart of the "other" server or something all the time. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
