Multiple backlogs to file against
![]()
Hi,
I am trying to tidy up our project in RTC and I want to create a new backlog to move pre 2013 stories into. The reason for this that in January we moved to using Kanban and we want to move all our old stories and tasks into a new backlog so that we can have a properly ranked backlog for our current work. We have thousands of work items and this is really slowing down opening the backlog.
I have created a new category called Pre 2013 and when I click on work items and select "Change Filed Against" I can change this but I cannot find how to navigate to this category or how to map it to a backlog plan.
If anybody could point me in the right direction of instructions of how to do this it would be very much appreciated.
Thanks
Caroline
|
Accepted answer
![]()
so you have iterations like this
Timeline Product (not in any year cycle) Year 1 and then you have Plans for each for Product - Product backlog for year 1 - Release backlog for quarter 1 plan - Release Backlog for q1-s1 you have a sprint backlog (execution items selected) for q1-s2 the same for q1-s3 the same for quarter 2 plan - Release Backlog for q2-s1 you have a sprint backlog (execution items selected) for q2-s2 the same for q2-s3 the same so to move workitems from one iteration to another you change their Iteration Planned move from q1-s2 to q2-s1, change the iteration planned. as there is a plan over each, this should move them as appropriate q1 is a release backlog plan etc. so you have plans that cover each iteration. now, the easiest way is to use eclipse, cause you can do a couple hundred at once. create a query that shows workitems by iteration, and pick just the iteration of concern. (note that if you have multiple 'plans' covering the same iteration this gets harder. ) edit the query results to show the workitem Iteration Planned attribute then select all the workitems you want to move, right click on the Iteration planned column of the query results panel, and select change Planned Iteration, then select the new iteration from the list presented.. if you have multiple plans per iteration time period, this is ok, I think as you said 'backlog', which is outside those.. but if you meant to one of the overlapping plans in the same iteration by team, then you will have to use drag/drop in eclipse to make that work, OR once the iteration is changed, also change the category/filed against, which is the TEAM (people) owner. (which matches your plan definitions, work(items), over time(iteration) by people (team)) Caroline Smith selected this answer as the correct answer
|
3 other answers
![]()
Hm.. I posted an answer here but it doesn't show.
You need an iteration labeled as the appropriate backlog, then run a query that shows the Iteration planned column (I am using Eclipse for this). select the workitems to move, right click on the iteration planned column, and select Change Iteration Planned, pick the iteration with the backlog as its container. Comments Thanks for the reply. I apologies in advance if I need this explained in baby language but I have tried everyting I can think of and I cannot seem to get these work items to actually move out of this backlog.
So if I create a new plan under the same project, create a backlog in there and an iteration under it then what should I do. I have a large feature with a couple of hundred use cases, stories and tasks under it and they all need to be moved as it to another backlog. It takes so long for our backlog to open with all of this old stuff.
I really dont understand how the categories fit into the bigger picture. ![]() FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Caroline, I tried to describe the fundamentals here: https://jazz.net/library/article/589 maybe it helps you to better understand how things work together.
|
![]()
Geoffrey Clemm (30.1k●3●30●35)
| answered Feb 25 '13, 10:16 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
You will want to model a "backlog" as an iteration, not as a category. So if you want an extra backlog, create a new iteration. Then to assign a work item to a different backlog, change the "planned for" field of the work item to the iteration for that backlog.
To bulk move a set of work items from one backlog to another, one approach is to open up a plan for the old backlog (a plan whose iteration is set to be the iteration of the old backlog), multi-select the work items you want to move to the new backlog, and change their planned-for property to be the iteration of the new backlog. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
Just to clarity, what I am trying to do is to move a couple of hundred work items from one backlog plan to another.