Work Items get moved from newly created folders to default
RTC 3.0.1.1 Windows client with a 3.0.1.1 server.
I have a product release backlog plan. I have created new team folders
and I have moved several items into those new folders.
Overnight (or after some time period), the work items appear back in
the default folders; like the "Top Items" folder.
Do you know if this is standard behavior for some types of work items?
I am aware that new work items get automatically assigned to the
"Defects & Enhancements" folder.
I have a product release backlog plan. I have created new team folders
and I have moved several items into those new folders.
Overnight (or after some time period), the work items appear back in
the default folders; like the "Top Items" folder.
Do you know if this is standard behavior for some types of work items?
I am aware that new work items get automatically assigned to the
"Defects & Enhancements" folder.
3 answers
RTC 3.0.1.1 Windows client with a 3.0.1.1 server.
I have a product release backlog plan. I have created new team folders
and I have moved several items into those new folders.
Overnight (or after some time period), the work items appear back in
the default folders; like the "Top Items" folder.
Do you know if this is standard behavior for some types of work items?
I am aware that new work items get automatically assigned to the
"Defects & Enhancements" folder.
I've setup a quick sample to try and reproduce this behavior. Can you help me understand your configuration? Based on the type of plan you mention, I assume you are using the Scrum Process Template and you've changed the default behavior (of no grouping) to group by folders. Looking at the plan types available, I see a Product Backlog and a Release Backlog but not a "produce release backlog" plan. It may not matter, but can you check the plan configuration and let me know which you have used? Do you have the plan configured to always load execution items?
Also, for the items that you moved, did they have parent items (and did you move those or leave them in the original location)? If you moved a parent, did you take the child with it or leave it in the original location? The type of work item might not matter -- but which types did you use (will help me match your situation)?
Thanks! Hopefully we can get this sorted for you.
Hi:
I am using a modified Scrum process template.
My plan type is a Release Backlog and I am looking at the View As: "Release Planning" and I've modified it to have the Grouping set to Folder.
I do not have this plan configured to "Always load execution items."
I just chekced one item and it did not have a parent.
Most of the moved items were epics, some are stories.
-Thanks
Maggie
I am using a modified Scrum process template.
My plan type is a Release Backlog and I am looking at the View As: "Release Planning" and I've modified it to have the Grouping set to Folder.
I do not have this plan configured to "Always load execution items."
I just chekced one item and it did not have a parent.
Most of the moved items were epics, some are stories.
-Thanks
Maggie
I setup folders and some work items and moved them around, then opened and closed the project several times since, changing PlannedFor and Rank on the items, but the folder assignments have held sticky the whole time. I'm not sure what else to try to reproduce the issue you have seen.
Do you have reproducible steps I can try?
Do you have reproducible steps I can try?