On May 12, 2009, at 3:39 PM, W. Martin Borgert wrote: > > On 2009-05-12 09:23, yoheeb wrote: >> 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? > > Neither nor. It's a well-thought "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. > > When we set up multiple trac instances we were completely aware > of private ticket and wiki page plugins. But the overhead of > managing this seemed (and still seems) to be relatively high > even compared to copying one ticket in a while manually from one > system to another. Note that both departments have also their > own wiki, SVN, etc. > > Thanks for the hint anyway. I'm sure for many similar situations > your suggestion is be the best solution!
The 0.10 version of TracForge did have a system for this, but it wasn't complete and definitely hacky. Did support full bi-directional updates though. --Noah --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
