Yes, this is intentional. Release Plans aggregate work items over the (child-)iterations and/or (child-)teams of the configured iteration and team, respectively. (see http://jazz.net/library/article/203 for details about the plan types).
Indeed, loading all work items would be a performance penalty too big.

I too think creating a new type would be the solution for the problem.

Hint: after you created the new type, query for all your scenario tasks and use the "Bulk edit" actions of the work item explorer view to change their type. This way, the manual work should be limited to a minimum.

--
MikeS
Jazz Agile Planning team

Peter Haumer wrote:

Hello.
I used to represent a scenario of a use case as a task. The Use Cases are
the top-level items in the top-level plan and the scenario tasks are
assigned to an iteration.

In RTC 1 the scenarios nicely appeared below the use cases in a grey font
when I expended them indicating with the color that they belonged to a
different iteration level. In RTC 2 they are now gone. For example, after I
turned my top-level plan into a Team Release Plan all the iteration folders
that were shown in this plan are empty. Unselecting the filter box for
Execution items has no effect here.

Has this done on purpose for RTC 2? Are the rules to
- only show plan and execution item of the same iteration level;
- only plan items of lower levels in the Iterations view, no execution
items? Is this for performance reasons?

Any way to get the old behavior back? If not that probably means more
clicking around for me or I have to create a new top-level work item type
for scenario and migrate my data manually. Hence, I need to maintain
two-levels of plan items, which seems to be more overhead. Anyone having
any other ideas?

Peter.


"mpomroy" <mpomroy> wrote in message
news:h4d4at$4ec$1@localhost.localdomain...
zrlrkewrote:
mpomroy wrote:
Getting up to speed on 2.0. I'm wondering about the releationship
between the release plan and iteration plans. Do scope items
always
live in the release plan or are they moved to the appropriate
iterations during planning sessions?

Been looking for docs on this so feel free to point me to the doco
if
it exists.

Thanks!


Yes, move each item to its iteration. Talking in Scrum lingo, an Epic

will stay on the level of a release and a story will be moved to a
sprint.

You then create a release plan (Team Backlog/Product Backlog) which
shows all Epics including their Stories. For the sprint, you create a

sprint backlog which shows the Stories including their implementation

tasks.

Check out http://jazz.net/library/article/203 for more details.

--
Cheers, Johannes
Agile Planning Team

Great article. We are using the OpenUP template - the most telling
difference I see is that the top level planning item is Epics whereas
in OpenUP it's Use Cases. Looks like in scrum you decompose epics
into Stories, what do you recommend for breaking down use cases?

Couple of thoughts we had are:
a) create fine grained use cases
b) create a new workitem type 'UC Scenario'

Thanks in advance!

Hello.
I used to represent a scenario of a use case as a task. The Use Cases are
the top-level items in the top-level plan and the scenario tasks are
assigned to an iteration.

In RTC 1 the scenarios nicely appeared below the use cases in a grey font
when I expended them indicating with the color that they belonged to a
different iteration level. In RTC 2 they are now gone. For example, after I
turned my top-level plan into a Team Release Plan all the iteration folders
that were shown in this plan are empty. Unselecting the filter box for
Execution items has no effect here.

Has this done on purpose for RTC 2? Are the rules to
- only show plan and execution item of the same iteration level;
- only plan items of lower levels in the Iterations view, no execution
items? Is this for performance reasons?

Any way to get the old behavior back? If not that probably means more
clicking around for me or I have to create a new top-level work item type
for scenario and migrate my data manually. Hence, I need to maintain
two-levels of plan items, which seems to be more overhead. Anyone having
any other ideas?

Peter.


"mpomroy" <mpomroy> wrote in message
news:h4d4at$4ec$1@localhost.localdomain...

zrlrkewrote:
mpomroy wrote:
Getting up to speed on 2.0. I'm wondering about the releationship
between the release plan and iteration plans. Do scope items
always
live in the release plan or are they moved to the appropriate
iterations during planning sessions?

Been looking for docs on this so feel free to point me to the doco
if
it exists.

Thanks!


Yes, move each item to its iteration. Talking in Scrum lingo, an Epic

will stay on the level of a release and a story will be moved to a
sprint.

You then create a release plan (Team Backlog/Product Backlog) which
shows all Epics including their Stories. For the sprint, you create a

sprint backlog which shows the Stories including their implementation

tasks.

Check out http://jazz.net/library/article/203 for more details.

--
Cheers, Johannes
Agile Planning Team

Great article. We are using the OpenUP template - the most telling
difference I see is that the top level planning item is Epics whereas
in OpenUP it's Use Cases. Looks like in scrum you decompose epics
into Stories, what do you recommend for breaking down use cases?

Couple of thoughts we had are:
a) create fine grained use cases
b) create a new workitem type 'UC Scenario'

Thanks in advance!

mpomroy wrote:

Getting up to speed on 2.0. I'm wondering about the releationship
between the release plan and iteration plans. Do scope items always
live in the release plan or are they moved to the appropriate
iterations during planning sessions?

Been looking for docs on this so feel free to point me to the doco if
it exists.

Thanks!

Yes, move each item to its iteration. Talking in Scrum lingo, an Epic
will stay on the level of a release and a story will be moved to a sprint.

You then create a release plan (Team Backlog/Product Backlog) which
shows all Epics including their Stories. For the sprint, you create a
sprint backlog which shows the Stories including their implementation
tasks.

Check out http://jazz.net/library/article/203 for more details.

--
Cheers, Johannes
Agile Planning Team

Hi mpomroy,

I am not sure I understnad your questions. Here my attempt:

Plans only show work items. work items do not live in plans.
Moving work items in plans will change the work item e.g. assign to an owner
or a team or a target iteration.
There are Top Level Work Items and Execution Items. They are treated different
in Release plans (at least were in some 2.0 betas I have briefly played with
teh release and I think I have seen it behaving a bit different.)

"Release Plans" typically only show and deal with Top Level Work Items. The
Work Items presented are also filteres by Release, sub iterations and Team
(Team Relaease Plan).
Given a release plan only work items would show up that are in its scope.
This means "Planned for" a scoped release and/or iterations ans project or
team area. The Release plans also consider planned for in sub iterations
of the coping iteration/release to be in scope.

You can show the work items by various groupings e.g. by iteration would
show the iteration as well as all defined sub iteration in the timeline this
allows to move work items between iterations. Other groupings allow to show
and change other aspects.

Plain Iteration plans just focus on the work items planned for an iteration
and the specific team. They typically show Top Level as well as execution
items.

Getting up to speed on 2.0. I'm wondering about the releationship
between the release plan and iteration plans. Do scope items always
live in the release plan or are they moved to the appropriate
iterations during planning sessions?

Been looking for docs on this so feel free to point me to the doco if
it exists.

Thanks!

Hope this helps,

Ralph
mailto:ralph.schoon@de.ibm.com