D
draco664
Hi all,
I've been given the task of creating a rather automated, constantly
updating project to track change requests.
Essentially, we are doing a release of code every month, for a number
of services, with many change requests.
This is the structure
Each Release has 4 phases (design, build, test, deploy)
Each Phase has one or more services (Say, service 1, service 2...)
Each Service has one or more Change Requests (Say, CR 1, CR 2...)
so the outline is like this.
Release 1
Design Tasks
Service 1
CR 1
Tasks for CR1, Service 1, Design
CR 2
...
Service 2
...
Build Tasks
Service 1
CR 1
Tasks for CR1, Service 1, Build
CR2
...
Service 2
...
Test Tasks
...
Deploy Tasks
...
Release 2
....
and so on.
So far, I've created macros that will allow the user to administer the
main structure (adding releases, services and CRs), but I'm a little
unsure I have the best way on how to add the actual tasks.
Currently, I have several CR templates (resourced, with predecessor
logic) that I want to copy into the main schedule. My current code
copies the tasks to the end of the project, then copies the individual
Design tasks to the design section of the plan, the build tasks to the
build section, and so on. And then I would delete the template's tasks
at the bottom of the schedule.
But there are several pitfalls I've run into, and fixing them is going
to take a lot of work. (Things like predecessor logic not copying) I
tried to figure out how to move the tasks, but there doesn't seem to
be a way to do that via VB.
I guess my question is this, is there a better way to import another
project into an existing one, where you can split the tasks up based
on where they should go in the existing plan?
(Or even if someone could point out to me the way to move tasks using
VB. That would work too!)
Thanks in advance,
Chris
I've been given the task of creating a rather automated, constantly
updating project to track change requests.
Essentially, we are doing a release of code every month, for a number
of services, with many change requests.
This is the structure
Each Release has 4 phases (design, build, test, deploy)
Each Phase has one or more services (Say, service 1, service 2...)
Each Service has one or more Change Requests (Say, CR 1, CR 2...)
so the outline is like this.
Release 1
Design Tasks
Service 1
CR 1
Tasks for CR1, Service 1, Design
CR 2
...
Service 2
...
Build Tasks
Service 1
CR 1
Tasks for CR1, Service 1, Build
CR2
...
Service 2
...
Test Tasks
...
Deploy Tasks
...
Release 2
....
and so on.
So far, I've created macros that will allow the user to administer the
main structure (adding releases, services and CRs), but I'm a little
unsure I have the best way on how to add the actual tasks.
Currently, I have several CR templates (resourced, with predecessor
logic) that I want to copy into the main schedule. My current code
copies the tasks to the end of the project, then copies the individual
Design tasks to the design section of the plan, the build tasks to the
build section, and so on. And then I would delete the template's tasks
at the bottom of the schedule.
But there are several pitfalls I've run into, and fixing them is going
to take a lot of work. (Things like predecessor logic not copying) I
tried to figure out how to move the tasks, but there doesn't seem to
be a way to do that via VB.
I guess my question is this, is there a better way to import another
project into an existing one, where you can split the tasks up based
on where they should go in the existing plan?
(Or even if someone could point out to me the way to move tasks using
VB. That would work too!)
Thanks in advance,
Chris