Can you automatically assign new tasks to a team?

[NikFr]

I'm trying to make use of team Kanban, but I'm running into a major blocker, which is that new tasks and issues aren't showing up in the backlog unless we manually assign them to a team - a step that's easily missed. Our work-around is a report that shows everything in a given portfolio that isn't assigned to the agile team, but that still means somebody has to go through and fix things. Is there any way to automatically assign tasks in a project to a given team so it will show up on the backlog? Inheriting from a parent task would work, too, just some method to avoid having to fiddle with things so much. By the same token, some sort of resiliency if somebody else unassigns a work item from a team, so it doesn't magically depart the agile team's purview entirely, would be really nice. Without something like this, Agile is just too fragile to be reliable. One wrong click can annihilate the whole sprint plan. If someone has a way to make this work better, I'd love to hear it. Nik Friedman TeBockhorst Engrain

[VicAl]

Hi Nik, It depends on how your creating your Tasks and Issues. If you create them using the Backlog tab in your Team's Agile view, it will automatically assign that team. Likewise if you open your Iteration (Sprint) and add a Task (aka Story) or Issue, it'll assign the team and also place the Task/Issue in the Iteration. You'll have to enter what project you want it to reside under if you use this method. So choose your poison. Enter the project with this method, or enter the team if you're adding them via the project. There's an auto assign if you create your issues via a Request menu. Then you can route to that team. I don't know of an equivalent for Tasks. WF doesn't force a Team assignment, as you may not want to assign a Team to a task (i.e. in our non-agile projects we assign individuals to a task and not the team). But you can write a report to show you all Tasks/Issues that don't have a Team Assignment and have it delivered to you once a week to remind you to clean those up. Hope that helps. Let me know if you have any questions or anything. Thanks.

[emilyd4009802]

What I had to do for tasks that weren't a part of a project, was to create a project just for those issues. When one comes in, convert it to a task and assign it to the backlog project. It showed up in Kanban then. Emily Duncan Carilion Clinic

[VicAl]

Hi Emily, You should be able to do this easier by going directly to the Kanban Team Backlog tab and click on New Stories (aka Tasks). It'll automatically assign the team and you can select the Project you want it to reside under. Same is true for the Issues (click Issues instead of Stories). Should save you the steps of converting an Issue to a Task etc.