In recent versions of RTC, a "backlog" is just one of your iterations,
where you assign work items that haven't yet targeted for a particular
time. A common way to look at those backlog work items is to create a
plan for that backlog iteration, and look at those work items via that plan.

Cheers,
Geoff

On 9/14/2011 10:38 AM, kfranciska wrote:

What is the difference between a plan and a backlog? Can anyone help
me understand this?

In recent versions of RTC, a "backlog" is just one of your iterations,
where you assign work items that haven't yet targeted for a particular
time. A common way to look at those backlog work items is to create a
plan for that backlog iteration, and look at those work items via that plan.

Is there a way to automatically assign work items to iterations?
If yes, how can i do?


For example: if a user (in our case a customer) creates and saves a work item, we want not to assign the bug or whatever directly to an release/iteration (That is the job of our product owner) so we forbid this in the permission options for customer.
But what we want to do is that this workitem automatically goes to the "produkt backlog" iteration.

Is this possible? How?



Further more, we would like to automatically shift workitems depending on their states into different iterations :-s
so, if any item gets the (custom) state "in implementation" we would like to move it to our Developement sprint.
for "in testing" to our QA sprint
"ready to deploy" -> deploy sprint
and so on...

How can our company resolve this matter?
Any ideas?

I haven't tried it, but you could try to specify a default and or calculated value provider type Iteration in the Work Item customization to set the planned for.

The other request changing iterations on states might be solvable that way too with a dependent value provider. My first thought however was proposing to use a process advisor as shown in the Extensions workshop in the library.

I would try it on a test server.