On Sep 10, 10:18 am, yoheeb <[email protected]> wrote:
> On Sep 10, 8:12 am, Olemis Lang <[email protected]> wrote:
>
>
>
> > On Wed, Sep 9, 2009 at 3:19 PM, Lukasz Szybalski <[email protected]>
> > wrote:
>
> > > Hello,
> > > I have 2 departments that need to use trac mostly for task management.
> > > Each of them have 2 different milestones and different version.
>
> > Perhaps Authz is what you need. Please read the std docs.
>
> > --
> > Regards,
>
> > Olemis.
>
> > Blog ES:http://simelo-es.blogspot.com/
> > Blog EN:http://simelo-en.blogspot.com/
>
> > Featured article:
> > Introducción a la API de Google Analytics
> > -http://feedproxy.google.com/~r/simelo-es/~3/iRzT5_lZg4c/introduccion-...
>
> I am not entirely your goal, but a combination of the multirepository
> search plugin, and intertrac links might be what you need to address
> this.
>
> so, 2 different tracs, different user groups/permissions and their own
> milestones. if a ticket is "REALLY" in project A it is created
> there. if it affects project B, you create a new ticket in project B,
> and put an intertrac link to the "real" ticket, in the real ticket you
> add an intertrac link to reference the "placeholder" ticket in project
> B.
>
> some other options:
> - 1 trac with "blocking" tickets in both milestones.
> - add a custom field :sub milestone, or similar.
> - along this line, 2 custom fileds, using the
> TracTicketChainedFieldsPlugin would work great to filter the second
> option
> make use of the Keywords field to add an additional filter criteria.
> I think the clearest way within the way TRAC works is to have 2
> tickets for everything. maybe the clone ticket plugin would be
> helpful, maybe you modify it a tad to automatically add a back link to
> the old ticket (and a forward link to the new ticket) if it doesn't do
> that automatically. you clone the ticket, then change the milestone.
>
> something else that actually might be useful is the Watchlist plugin.
> it's not obvious at first, but could have something there for you.
>
> There is also a TracDependencyPlugin for intertrac ticket dependencies
> and summary tickets I really have no idea how it works though.
> not sure that helped any.
Authz is more for svn I guess.
intertrac might not work as wiki is not used as much.
In my case I have a programming dept, and billing dept. Two separate
entity. One has milestones for programs, while another has milestones
like "August statement", "Bills"...
One uses trac in normal way while another is using mostly task type of
tickets. We don't want to mix the milestones so separate instance of
trac seems like a best solution.
multirepository search plugin might be useful.
I don't want user from one group pick a milestone, version from
another group except for the common one. aka billing person does not
need to see 10 milestones that are available for programmer, and
programmer doesn't need to see the 10 milestones available for billing
person.
So 2 separate instances of trac seem to be what we need. With that in
mind I will need to somehow move from one trac to another. So if a
programmer gets a bill for something, he assigns it to somebody, or
some special milestone, and that ticket gets moved over to billing
trac where a billing person sees a new ticket# that came from a
programmer.
Thoughts.
Thanks,
Lucas
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
