Tracking work item in multiple timelines

I was planning to use this approach (duplicate work items) but I'm not satisfied with how it behaves when using different approval processes for 1.0 and 2.0 (i.e. iteration types with deliver(server) precondition).

For example, I have a defect that resulted in a code change in 1.0 that we also want it in 2.0.  I duplicated the original work item, set the planned for to 2.0, and assigned it to a dev resource to merge (accept) into 2.0.  The dev accepts the change set (assume no conflicts) but when they deliver RTC looks at the approvals on the original work item (planned for 1.0) using the process and teams from 2.0.

Ideally I want the delivery to 1.0 and 2.0 to be tracked independently and require different approvals. 

Work arounds I've considered:
1)  Remove the approvals from the original work item before duplicating (this will force the second delivery to set approvals)
2)  Use patches (rather than accepting), a patch will result in a new change set that can be associated with the duplicated work item (rather than the original)


Is there a better approach to tracking changes to multiple code streams?

Is there a way to track a Defect Work Item in multiple timelines? For
example, we currently have 2 releases, 1.0 is in maintenance mode, 2.0
is in pre-GA development. If we find a defect in the 1.0 release
that's also occurring in the 2.0 pre-GA development, how do we
account for this in the Iteration plans when these plans are
different for the 2 releases. If I select Planned For = 1.0 it won't
appear in the 2.0 Iteration plan and vice versa.

Is there a best practice for managing defects that need to be fixed in
multiple timelines? I looked in the Docs but couldn't find anything.

I would suggest to duplicate and link the work item in order to track it
in both timelines.

--
Regards,
Patrick
Jazz Work Item Team

Is there a way to track a Defect Work Item in multiple timelines? For
example, we currently have 2 releases, 1.0 is in maintenance mode, 2.0
is in pre-GA development. If we find a defect in the 1.0 release
that's also occurring in the 2.0 pre-GA development, how do we
account for this in the Iteration plans when these plans are
different for the 2 releases. If I select Planned For = 1.0 it won't
appear in the 2.0 Iteration plan and vice versa.

Is there a best practice for managing defects that need to be fixed in
multiple timelines? I looked in the Docs but couldn't find anything.

I would suggest to duplicate and link the work item in order to track it
in both timelines.

--
Regards,
Patrick
Jazz Work Item Team

Thanks...is there an easy way to create a duplicate of a work item once I created the original in one timeline? I only see options for moving to another Project Area or extracting text to create a new work item. This last option could work and avoid duplicating the Defect recreate text, but it would be nice to have an option that duplicates the other fields also.

The operation is "Move/Copy to new project area".
The first page of the wizard will ask you whether you want to "move" or
"copy".
Select "copy".
And note that you can select the same project area as the original, so
you can use this operation to create a copy in the same project area as
the original.

Cheers,
Geoff

miwalker wrote:

zrlpaswrote:

Is there a way to track a Defect Work Item in
multiple timelines? For
example, we currently have 2 releases, 1.0 is in maintenance mode,
2.0
is in pre-GA development. If we find a defect in the 1.0 release
that's also occurring in the 2.0 pre-GA development, how do we
account for this in the Iteration plans when these plans are
different for the 2 releases. If I select Planned For = 1.0 it
won't
appear in the 2.0 Iteration plan and vice versa.

Is there a best practice for managing defects that need to be fixed
in
multiple timelines? I looked in the Docs but couldn't find
anything.
I would suggest to duplicate and link the work item in order to track
it
in both timelines.

Another approach is to have a single "defect" work item, but then create
two task work items (one for each release), both linked to that defect
work item. This would allow you to keep the discussion about the defect
itself in one work item, while having task-specific discussions in the
task work items.

Cheers,
Geoff

Patrick Streule wrote:

Is there a way to track a Defect Work Item in multiple timelines? For
example, we currently have 2 releases, 1.0 is in maintenance mode, 2.0
is in pre-GA development. If we find a defect in the 1.0 release
that's also occurring in the 2.0 pre-GA development, how do we
account for this in the Iteration plans when these plans are
different for the 2 releases. If I select Planned For = 1.0 it won't
appear in the 2.0 Iteration plan and vice versa.

Is there a best practice for managing defects that need to be fixed in
multiple timelines? I looked in the Docs but couldn't find anything.

I would suggest to duplicate and link the work item in order to track it
in both timelines.

The operation is "Move/Copy to new project area".
The first page of the wizard will ask you whether you want to "move" or
"copy".
Select "copy".
And note that you can select the same project area as the original, so
you can use this operation to create a copy in the same project area as
the original.

Cheers,
Geoff

miwalker wrote:

zrlpaswrote:

Is there a way to track a Defect Work Item in
multiple timelines? For
example, we currently have 2 releases, 1.0 is in maintenance mode,
2.0
is in pre-GA development. If we find a defect in the 1.0 release
that's also occurring in the 2.0 pre-GA development, how do we
account for this in the Iteration plans when these plans are
different for the 2 releases. If I select Planned For = 1.0 it
won't
appear in the 2.0 Iteration plan and vice versa.

Is there a best practice for managing defects that need to be fixed
in
multiple timelines? I looked in the Docs but couldn't find
anything.
I would suggest to duplicate and link the work item in order to track
it
in both timelines.

Geoff,

Are you sure you can select the same Project Area when choosing to Move or Copy to another Project Area?

I tried both Move and Copy but neither allows me to choose the Project Area the work item was created in. Only the other Project Areas appear.

Sure enough, just tried it again, and couldn't select the same project
area. Could have sworn my earlier try succeeded ... I must have had two
project areas named similarly open when I tried it before.

So it looks like you have to copy it to another project area (with a
similar process), and then "move" it back. I've submitted work item
103449 to allow one to specify the same project area when "copy" is the
operation selected.

Cheers,
Geoff

miwalker wrote:

gmclemmwrote:
The operation is "Move/Copy to new project area".
The first page of the wizard will ask you whether you want to
"move" or
"copy".
Select "copy".
And note that you can select the same project area as the original,
so
you can use this operation to create a copy in the same project area
as
the original.

Cheers,
Geoff

miwalker wrote:
zrlpaswrote:
Is there a way to track a Defect Work Item in
multiple timelines? For
example, we currently have 2 releases, 1.0 is in maintenance mode,
2.0
is in pre-GA development. If we find a defect in the 1.0 release
that's also occurring in the 2.0 pre-GA development, how do we
account for this in the Iteration plans when these plans are
different for the 2 releases. If I select Planned For = 1.0 it
won't
appear in the 2.0 Iteration plan and vice versa.

Is there a best practice for managing defects that need to be fixed
in
multiple timelines? I looked in the Docs but couldn't find
anything.
I would suggest to duplicate and link the work item in order to
track
it
in both timelines.

Geoff,

Are you sure you can select the same Project Area when choosing to
Move or Copy to another Project Area?

I tried both Move and Copy but neither allows me to choose the Project
Area the work item was created in. Only the other Project Areas
appear.

Ooops. It isn't the "Move/Copy" operation that should be used in this
case ... it is the "Duplicate" operation (which duplicates the work item
into the same project area).

Cheers,
Geoff

Geoffrey Clemm wrote:

Sure enough, just tried it again, and couldn't select the same project
area. Could have sworn my earlier try succeeded ... I must have had two
project areas named similarly open when I tried it before.

So it looks like you have to copy it to another project area (with a
similar process), and then "move" it back. I've submitted work item
103449 to allow one to specify the same project area when "copy" is the
operation selected.

Cheers,
Geoff

miwalker wrote:
gmclemmwrote:
The operation is "Move/Copy to new project area".
The first page of the wizard will ask you whether you want to
"move" or
"copy".
Select "copy".
And note that you can select the same project area as the original,
so
you can use this operation to create a copy in the same project area
as
the original.

Cheers,
Geoff

miwalker wrote:
zrlpaswrote:
Is there a way to track a Defect Work Item in
multiple timelines? For
example, we currently have 2 releases, 1.0 is in maintenance mode,
2.0
is in pre-GA development. If we find a defect in the 1.0 release
that's also occurring in the 2.0 pre-GA development, how do we
account for this in the Iteration plans when these plans are
different for the 2 releases. If I select Planned For = 1.0 it
won't
appear in the 2.0 Iteration plan and vice versa.

Is there a best practice for managing defects that need to be fixed
in
multiple timelines? I looked in the Docs but couldn't find
anything.
I would suggest to duplicate and link the work item in order to
track
it
in both timelines.

Geoff,

Are you sure you can select the same Project Area when choosing to
Move or Copy to another Project Area?
I tried both Move and Copy but neither allows me to choose the Project
Area the work item was created in. Only the other Project Areas
appear.

Ooops. It isn't the "Move/Copy" operation that should be used in this
case ... it is the "Duplicate" operation (which duplicates the work item
into the same project area).

Cheers,
Geoff

Geoffrey Clemm wrote:

Sure enough, just tried it again, and couldn't select the same project
area. Could have sworn my earlier try succeeded ... I must have had two
project areas named similarly open when I tried it before.

So it looks like you have to copy it to another project area (with a
similar process), and then "move" it back. I've submitted work item
103449 to allow one to specify the same project area when "copy" is the
operation selected.

Cheers,
Geoff

miwalker wrote:
gmclemmwrote:
The operation is "Move/Copy to new project area".
The first page of the wizard will ask you whether you want to
"move" or
"copy".
Select "copy".
And note that you can select the same project area as the original,
so
you can use this operation to create a copy in the same project area
as
the original.

Cheers,
Geoff

miwalker wrote:
zrlpaswrote:
Is there a way to track a Defect Work Item in
multiple timelines? For
example, we currently have 2 releases, 1.0 is in maintenance mode,
2.0
is in pre-GA development. If we find a defect in the 1.0 release
that's also occurring in the 2.0 pre-GA development, how do we
account for this in the Iteration plans when these plans are
different for the 2 releases. If I select Planned For = 1.0 it
won't
appear in the 2.0 Iteration plan and vice versa.

Is there a best practice for managing defects that need to be fixed
in
multiple timelines? I looked in the Docs but couldn't find
anything.
I would suggest to duplicate and link the work item in order to
track
it
in both timelines.

Geoff,

Are you sure you can select the same Project Area when choosing to
Move or Copy to another Project Area?
I tried both Move and Copy but neither allows me to choose the Project
Area the work item was created in. Only the other Project Areas
appear.


Thanks Geoff,

I think we're going to go with creating a separate task for the separate Release.