From: Chris Schlaeger (cs_at_suse.de)
Date: Tue Aug 16 2005 - 03:58:01 CEST
From: Chris Schlaeger <cs@suse.de> Message-Id: <20050816015801.E79BA24A4F9A@einstein.suse.de> Date: Tue, 16 Aug 2005 03:58:01 +0200 (CEST) Subject: [taskjuggler] Re: Reusing resources
Have a look at the examples that come with the source. The BigProject shows exactly what you are looking for. It's easy to share resource definitions between several projects.
Resource IDs are global, so you can freely move them between teams. This only has an impact on the allocation when teams are allocated. To avoid changes affecting the past, see the section on project tracking in the manual.
Resources can be added to the global definition, but not removed. Removing resources can break projects. When a new resource joins put it on vacation until the join date. When a resource leaves, put it on vacation from that day on. Vacation dates must be in the interval 1971-01-01 to 2030-01-01. See the reference for 'vacation' for more details.
Role or skill based allocation is on our todo list, but unlikely to happen any time soon.
Chris
-- TaskJuggler Developer -- To unsubscribe, email the address listed in the List-Unsubscribe header For additional commands, email: taskjuggler-help@suse.com
This archive was generated by hypermail 2.1.7 : Tue Aug 16 2005 - 03:58:09 CEST