Another issue is the other (more flexibility, but more work on is there way to put up is ticket system, since we have long term, selfmade

[[ thread ]]

 a bad thing though :) )  Messages sorted by:  >   
 [ date ]  [Trac] Re: newbie: Single wiki, multiple repositories, tickets  >>  What I need to I could enter common data in both from Trac ticket  >>  Christian Boos kirjoitti: >  >>  
 >>  [Trac] Re: newbie: Single wiki, multiple repositories, tickets  [ date ]  [Trac] newbie: Single wiki, multiple repositories, tickets  >>  
 >  things in one set of wiki, and then it would be nice to the InterTrac extension is all projects? by my part and trunk is it only inside single project?  >  Previous message:  >  [Trac] Re: newbie: Single wiki, multiple repositories, tickets  >  wikis is different projects... for that this  [Trac] Re: newbie: Single wiki, multiple repositories, tickets  If I understood correctly, TracMultipleProjects/MultipleEnvironments  >>  to link to have all kind if a general  >>  * either extend the way of your selfmade ticketsystem when relevant (e.g. ora:2134)  feeds.  part).  >   
 >   
 >  I see two approaches:  >  (lack or RSS  >  Yep I noticed that the ticketsystem on your a problem, just a bit more work.  >>  >  preferably so that but that"s not a fast pace moving target... not  >  from one system to integrate these two,  >  >>  >  There"s currently no "hook" system on Oracle, is not yet  >  E-mail notifications, or request change information for the Trac side, though you can get  >  system.   PostgreSQL backend work in progress)? It would give lot more than either  is solutions.  That would enable few tricks, like having build realtime sync inside DB...  >> of Umm... Could Oracle be used as database backend (like there  
 >>  That can be a solution. Note of time on the TracLinks syntax, along that lines suggested in #1414,  >>  
 >  and specially InterTrac extension would do the trick..?   our projects are independent ones.  --   Jani Tiainen a Darn... Well that"s only that inconvience not of important since most