A question about iteration plan hieararchy in Team Artifact

lilo wrote:

what's the relationship between the iteration hierarchy of Team
Artifact->Project area->plans and process iteration hierarchy
in project area?

The Plans node in the Team Artifacts view shows only those iteration

that plan a release. In the Project Area editor, select an iteration,
and press Edit Properties. Set/Unset the 'A release is scheduled for
this iteration' and the corresponding node will show up in the TAV or not.

The arrangement in the Plan node is the following: All current
iterations come first as top-level node (e.g. in the JUnit sample
project 4.4m2 and 4.4). All remaining iterations reflect the hierarchy
defines in the PA editor starting with the development line. Because of
that, some iterations (current) may appear twice.

--
Cheers, Johannes
Agile Planning Team

that plan a release. In the Project Area editor, select an iteration,
and press Edit Properties. Set/Unset the 'A release is scheduled for
this iteration' and the corresponding node will show up in the TAV or not.

The arrangement in the Plan node is the following: All current
iterations come first as top-level node (e.g. in the JUnit sample
project 4.4m2 and 4.4). All remaining iterations reflect the hierarchy
defines in the PA editor starting with the development line. Because of
that, some iterations (current) may appear twice.


Agile Planning Team

Thanks, you are right!
However when I tried to refect the iteration structure after changing the process iteration according to the rules you mentioned, I had to restart RTC client, no matter I refreshed in TAV or re-connect the project, it didn't work.
is it a RTC1.0 defect or the default design? I think re-start RTC client is overladen.

lilo wrote:

However when I tried to refect the iteration structure after changing
the process iteration according to the rules you mentioned, I had to
restart RTC client, no matter I refreshed in TAV or re-connect the
project, it didn't work.
is it a RTC1.0 defect or the default design? I think re-start RTC
client is overladen.

Well, that's a defect of an overeagerly cache. I have filed a defect to
track this
(https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/58858)

--
Cheers, Johannes
Agile Planning Team

Well, that's a defect of an overeagerly cache. I have filed a defect to
track this
(https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/58858)

--
Cheers, Johannes
Agile Planning Team


Thanks zrlrke, hope this can be fixed soon.