Team area heirachy
It is possible to arrange the different different teams.
Also a team area can have its own time line.
But when we create team area heirarchy like Project area x-> Team Area 1-> Team area 11,
for team area 11 I can no more set different timeline.
Is that intended? or is some settings missing..
Accepted answer
I've created work item Allow a nested team area to specify its own timeline (324119) requesting this functionality.
2 other answers
Hi Ratheesh
Team areas inherit the process and timeline of their parent, which can be the project area or a parent team area. They can customize the aspects of the process and when allowed, override all or portions of it.
Check this IBM infocenter URL:
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m5/index.jsp?re=1&topic=/com.ibm.jazz.platform.doc/topics/c_team_area.html&scope=null
Let me know if this helps.
Team areas inherit the process and timeline of their parent, which can be the project area or a parent team area. They can customize the aspects of the process and when allowed, override all or portions of it.
Check this IBM infocenter URL:
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m5/index.jsp?re=1&topic=/com.ibm.jazz.platform.doc/topics/c_team_area.html&scope=null
Let me know if this helps.
I'm relatively certain it's by intention. The 4.0.5 documentation has this to say:
See https://jazz.net/forum/questions/68815/project-timeline as well. A statement there about "top level teams" is of particular merit.
Timeline
A timeline represents an area of activity within a project that typically has its own schedule, deliverables, teams, and process. For example, a project with both new product release development and current product maintenance might define these two efforts in separate timelines because they have different delivery schedules, teams, and processes. Within a timeline, you can create a hierarchy of iterations where top-level iterations represent releases and child iterations represent milestones within those releases.
You can designate one of your timelines as the project timeline. All of the predefined process templates except for the Unconfigured Process template specify a project timeline. The project timeline defines the project area start and end dates along with the iteration breakdown of those dates. The project timeline differs from your other timelines in the following ways:
- The project timeline iterations apply to the project area. This means that if the project timeline process is customized for the current iteration, that customized process affects any artifacts associated with the project area.
- All team areas that do not have an explicit custom timeline set are governed by the process of the project timeline.
Comments
1 vote