RTC Formal Planning showing incorrect load and tasks at wrong place
![]() I have a client who is using formal planning process in RTC version 6.0.5. I have following team structure
Parent Team
- Child Team A
- Child Team B
I have quarterly iterations against which I have created quarterly plan for Parent Team. I have a plan for 2018 Q2. I have same resource in Child Team A and Child Team B. I allocated the resource from 1st Mar to Jun 30 60% to Child Team A and 40% to Child Team B. The load bar in the plan shows total available hours to 3 times actual available hours for the resource. The total available hours for the resource for both teams is e.g. 400 hours however on the load bar it shows 1200 hours.
I have a second scenario where on the resource tab all tasks assigned to the against Child Team A are shown below Child Team B. Child Team B tasks also appear against Child Team B.
I am at a loss what can be the problem. I had CLM version 6.0.2 installed in which this problem existed. I upgraded to 6.0.5 and the problem still persists.
|
One answer
![]()
Ralph Schoon (61.8k●3●36●43)
| answered Apr 09 '18, 4:40 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER In my experience over the years the problem was more often than not the (wrong) configuration of RTC rather than a defect in RTC. From the description, I don't know what could be the reason here. One factor I am aware of that can cause "more available hours than expected" is that some users specify "parallel" iterations. e.g. an iteration Milestone 1 from Feb 1 to March 3 and another iteration ReleaseTest from Feb 1 to March 6. This would cause more than double of the time counted. I would also carefully check where each resource is really assigned and with what percentage. Maybe test this out in a small test system with only few members.
Comments We do have parallel iterations in the project area.
Timelines can be parallel. What is not supported is defining overlapping iterations within one timeline. Within a timeline iterations of each level must partition the interval they specify.
|