[prev in list] [next in list] [prev in thread] [next in thread] 

List:       trac
Subject:    [Trac] Re: Milestone or Component Hierarchy?
From:       "Culapov Andrei" <andrei2102 () gmail ! com>
Date:       2008-05-31 17:30:10
Message-ID: b54ac2510805311030q69e81cf7x41ee7074aff64a7a () mail ! gmail ! com
[Download RAW message or body]


Hi Rupert,
For the plugins that didn't have a 0.11 version we fixed them to work.
For the majority of them we posted patches to the original plugins. If
you browse the code http://code.optaros.com/trac/oforge/browser/trunk
you will see that we splitted the plugins in two categories:
 - trac-hacks - here you will see some plugins imported from trac-hacks directly
 - forks - the plugins that didn't worked or had some bugs and we had
to patch them

On Fri, May 30, 2008 at 10:14 PM, rupert thurner
<rupert.thurner@gmail.com> wrote:
>
> according to http://code.optaros.com/trac/oforge/wiki/AssembledComponents
> you integrated a lot of plugins which do not support 0.11? did you
> change them, or you run them like that?
>
> rupert.
>
> On May 30, 3:37 pm, "Culapov Andrei" <andrei2...@gmail.com> wrote:
>> Hi,
>> Maybe you need for every project a new trac environment. We developed
>> a plugin that addresses that problem, that makes easy management of
>> multiple trac environments.http://code.optaros.com/trac/oforge/browser/trunk/plugins/oforgeplugin
>>
>> On Thu, May 29, 2008 at 9:23 PM,  <swiftm...@gmail.com> wrote:
>>
>> > Hello. At the company I work at we are starting to use Trac for
>> > keeping track of all the tasks we need to do. But we have a lot of
>> > products and projects. We have been using Trac for a few months and
>> > already our milestone and component list is getting large. I am here
>> > to ask if it is possible to set up a simple hierarchy of say two or
>> > maybe three levels within the milestones or the components. I will
>> > give two examples.
>>
>> > Multiple Components:
>> > There is an overall milestone we want to accomplish that contains many
>> > different types of tasks within a bunch of different products.
>> > Currently one thought is two make the components the name of different
>> > products/parts/prototypes thus within the overall milestone, the
>> > components separate out the tickets per product or part. But this
>> > setup means we are going to have a hundred or so components. There is
>> > also no organization within the components with this setup. Ideally
>> > the hierarchy in this sense would be Milestone
>> >        Part#1 Component
>> >                Tests, Research, Software Dev (three sub components).
>>
>> > Multiple Milestones:
>> > I am in more favor of this approach. Instead of making tons of
>> > components, do the hierarchy with Milestones. For an example we could
>> > have the milestones setup like this.
>> > ST-2400 (Top Milestone)
>> >        GPS Unit (sub milestone)
>> >                -Components separate tickets
>> >                -Tests, Research, Software Dev....
>> >        GeoSync Unit
>> >                -Components...
>> >        Frame and Chassis
>> >                -Components...
>> >        Wireless Com Unit
>> >                -Components...
>>
>> > Is there anyway to accomplish this in Trac? Perhaps there is some sort
>> > of mod or plugin that may accomplish this?
>>
>> > If we want to implement this hierarchy into the Trac code ourself,
>> > would this be a huge task?
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to trac-users-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic