Can't see my dev line when creating a work item
Hi. I've created a new team area (top level) for a seperate piece of development and have created a new dev line for the team as well. I have then created iterations for this dev line. This all worked fine.
However, when I create a new Work Item, and choose the team I created in the "Filed Against" drop down, the iterations I added are not available in the "Planned For" drop down. Rather, the ones I can see are for the top level dev line which other teams are using. Even when I save, close and reopen the work item it does not work.
Hope someone can point out my obvious mistake.
TIA
Cheers, Andrew
However, when I create a new Work Item, and choose the team I created in the "Filed Against" drop down, the iterations I added are not available in the "Planned For" drop down. Rather, the ones I can see are for the top level dev line which other teams are using. Even when I save, close and reopen the work item it does not work.
Hope someone can point out my obvious mistake.
TIA
Cheers, Andrew
3 answers
The "Filed Against" drop down only shows iterations which you've flagged
as producing a release. To configure this, open the project area and
edit the properties of your iterations. You'll see a checkbox labelled
"A release is scheduled for this iteration".
Jared Burns
Jazz Process Team
al94781 wrote:
as producing a release. To configure this, open the project area and
edit the properties of your iterations. You'll see a checkbox labelled
"A release is scheduled for this iteration".
Jared Burns
Jazz Process Team
al94781 wrote:
Hi. I've created a new team area (top level) for a seperate piece of
development and have created a new dev line for the team as well. I
have then created iterations for this dev line. This all worked
fine.
However, when I create a new Work Item, and choose the team I created
in the "Filed Against" drop down, the iterations I added
are not available in the "Planned For" drop down. Rather,
the ones I can see are for the top level dev line which other teams
are using. Even when I save, close and reopen the work item it does
not work.
Hope someone can point out my obvious mistake.
TIA
Cheers, Andrew
"Jared" == Jared Burns <jared_burns> writes:
Jared> The "Filed Against" drop down only shows iterations which you've
Jared> flagged as producing a release. To configure this, open the project
Jared> area and edit the properties of your iterations. You'll see a checkbox
Jared> labelled "A release is scheduled for this iteration".
So what do you envision as the use cases for iterations _not_ so marked?
--
John Kohl
Senior Software Engineer - Rational Software - IBM Software Group
Lexington, Massachusetts, USA
jtk@us.ibm.com
<http>
An example would be if you have a set of milestone iterations that you
target your work to and then those iterations are broken down into
functional iterations that have different processes.
We used to do this on our server. Each milestone was broken down into
two iterations, "development" and "stabilization". The stabilization
iteration had a more strict process than the development iteration...
but these iterations didn't produce their own releases so we would not
target work items to them.
Jared Burns
Jazz Process Team
John T. Kohl wrote:
target your work to and then those iterations are broken down into
functional iterations that have different processes.
We used to do this on our server. Each milestone was broken down into
two iterations, "development" and "stabilization". The stabilization
iteration had a more strict process than the development iteration...
but these iterations didn't produce their own releases so we would not
target work items to them.
Jared Burns
Jazz Process Team
John T. Kohl wrote:
"Jared" == Jared Burns <jared_burns> writes:
Jared> The "Filed Against" drop down only shows iterations which you've
Jared> flagged as producing a release. To configure this, open the project
Jared> area and edit the properties of your iterations. You'll see a checkbox
Jared> labelled "A release is scheduled for this iteration".
So what do you envision as the use cases for iterations _not_ so marked?