[closed] Backlog Iteration
I was reading about the Backlog Iteration setting in the Project Area Process Configuration. It says:
Work Items with the 'Planned For' attribute set to the iteration marked 'backlog iteration' appear on the backlog plan. Per timeline you can mark one iteration as the backlog iteration.
What does RTC actually do with this information? We had created an iteration & plan named Product Backlog long before I learned about this setting & I think the behavior was just as described above without naming a backlog iteration.
Chris
Work Items with the 'Planned For' attribute set to the iteration marked 'backlog iteration' appear on the backlog plan. Per timeline you can mark one iteration as the backlog iteration.
What does RTC actually do with this information? We had created an iteration & plan named Product Backlog long before I learned about this setting & I think the behavior was just as described above without naming a backlog iteration.
Chris
The question has been closed for the following reason: "The question is answered, right answer was accepted" by rschoon Aug 27 '16, 1:31 p.m.
Accepted answer
While this is an old question, it is nevertheless one of the first hits one finds when searching for the meaning of the Backlog mark.
So after a little research in RTC 5.0.2, I found these additional aspects:
So after a little research in RTC 5.0.2, I found these additional aspects:
- The "Current Plans" view will show all plans for any Iteration that is marked as "current" plus the Backlog iteration(s)
- The new "QuickPlanner" provides a feature to "Triage to Backlog", for which to work you need a known Backlog iteration (as opposed to an iteration called "Backlog")
6 other answers
I was reading about the Backlog Iteration setting in the Project Area Process Configuration. It says:
Work Items with the 'Planned For' attribute set to the iteration marked 'backlog iteration' appear on the backlog plan. Per timeline you can mark one iteration as the backlog iteration.
What does RTC actually do with this information? We had created an iteration & plan named Product Backlog long before I learned about this setting & I think the behavior was just as described above without naming a backlog iteration.
Chris
Hey Chris,
The type of plan has some preconfigured views (like work break down) and some filters. The idea is that all plan types are not the same and it may differ which things you want to see where or perhaps even which workitems you want where. This can be additioanlly limited by using iteration types and setting a type on your iteration making special permissions on rules apply for the time in your project lifecycle when you are in that particular iteration. Hope it makes sence :-)
As far as I can tell, all it is used for is to initialize the plan type when you create a new plan (i.e. it creates a "product backlog" plan if you select the iteration that is declared to be the backlog iteration). But you can easily just manually select "product backlog" as the type of your plan, so this doesn't save you any significant effort.
Set the BacklogIteration in this dialog:
(Open Project area in e.g. Eclipse), then:
Process Configuration -> Project Configuration -> Configuration Data -> Planning -> General
In the list to the right, choose your backlog iteration and press the small backlog icon next to "Backlog Iteration"
(Open Project area in e.g. Eclipse), then:
Process Configuration -> Project Configuration -> Configuration Data -> Planning -> General
In the list to the right, choose your backlog iteration and press the small backlog icon next to "Backlog Iteration"
