Redmine

I am not sure I completely understood what you are looking for, but the example you gave of your boss being able to go to one "Parent" project and see all Roadmap of all the parts is something I am definitely looking for. The way I understand this to work would be to have a Parent project -- "Network Core" which would hold project versions/roadmap info. Then I would like to make sub-projects (for the technical work) -- for example: "core switches" , LDAP structure, ...

+ Network Core (versions -- phase 1, phase 2, phase 3, etc) |-Firewall - (task 1-[associated with phase 1], task 3-[associated with phase 2], task 10-no version association) |-Core Switches (task 2-[associated with Phase 1], task 15-[associated with Phase 3]) |-Authentication Services (task 5-[associated with phase 2])

When my boss (the manager) goes to the Parent - Network Core and looks at the Roadmap (or Gantt) he sees all the tasks associated with each phase/version from all the sub-projects & has a good idea of how the entire project is progressing -- despite the fact that several techs are be working on separate technologies at once. Equally importantly, each tech will be able to see the impact of their work on the team - especially since our team is NOT co-located.

Is this the same as you were discussing? I am definitely behind making this type of large project management easy to coordinate between many sub-projects. In fact, I think finding some way to let this scale is critical to my organization -- in the near future.

Opps -- I forgot to put my "Graphic" in the pre tags.

+ Network Core (versions -- phase 1, phase 2, phase 3, etc) 
|-Firewall - (task 1-[associated with phase 1], task 3-[associated with phase 2], task 10-no version association) 
|-Core Switches (task 2-[associated with Phase 1], task 15-[associated with Phase 3]) 
|-Authentication Services (task 5-[associated with phase 2])

Pretty close...In short I wanted the ability to assign a sub project issue to a "target version" of the parent. As of now, the parent project has no association of "target version" of its children projects. What I would like to have is the ability to do a query on "target version" of the sub projects within the main project issues list. As of now, all my sub projects have the same target version schema and iteration date/due date. This makes my manager life easier when he goes to the main projects and does a query.

+1 for issues in a child project to be assignable to a parent project's version, this could be very handy for modular projects