Long living Release Backlog
For planning, we are using the following iteration structure
Main Development (timeline)
Product Backlog
Release Backlog
Sprint01
Sprint02
.
.
Sprint n
In 3.0.1.4, when sprints are completed, we archive the sprint and the iteration (and work items) were no longer included in our Release Backlog plan. After upgrading to 4.0.3, archiving does not remove them from Release Backlog plan which is impacting our Release Backlog plan performance as well as a crash (work item -> https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=283781). As a work around, I created a new "Complete" iteration as a peer to the Release Backlog and move complete sprints under it.
Is the behavior change between 3.0.1.4 and 4.0.3 design or a bug (behavior -> including archived Sprints in the Release Backlog)?
If by design, what is the recommended way to manage a Release Backlog that lives a long time (potentially for ever)?
Main Development (timeline)
Product Backlog
Release Backlog
Sprint01
Sprint02
.
.
Sprint n
In 3.0.1.4, when sprints are completed, we archive the sprint and the iteration (and work items) were no longer included in our Release Backlog plan. After upgrading to 4.0.3, archiving does not remove them from Release Backlog plan which is impacting our Release Backlog plan performance as well as a crash (work item -> https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=283781). As a work around, I created a new "Complete" iteration as a peer to the Release Backlog and move complete sprints under it.
Is the behavior change between 3.0.1.4 and 4.0.3 design or a bug (behavior -> including archived Sprints in the Release Backlog)?
If by design, what is the recommended way to manage a Release Backlog that lives a long time (potentially for ever)?
One answer
Ah, based on your comment, perhaps it is a plan configuration thing. If you look at the plan filter settings, does it exclude resolved items? The archiving action on the sprint should have no effect on plan item visibility.
Comments
showing 5 of 6
show 1 more comments
Comments
Millard Ellingsworth
FORUM ADMINISTRATOR / JAZZ DEVELOPER Oct 08 '13, 10:36 p.m.Erik anderson
Oct 09 '13, 7:47 a.m.Millard Ellingsworth
FORUM ADMINISTRATOR / JAZZ DEVELOPER Oct 09 '13, 11:32 a.m.Erik anderson
Oct 09 '13, 2:24 p.m.