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 a...

What about just publishing calendar reports to an ics feed? Nik Friedman TeBockhorst Engrain

Thanks for the quick turn on that, Jacob! I just saw those options pop up. I have one other question: How is the team backlog populated? Which tasks end up there - only ones assigned to the team? I did notice if I unassign a task from the team, it falls off of the board, but it still seems to stay i...

Hi all - I'm trying to convert my team workflow over to Kanban, and I need a little help in how to go about this: Backlog view - this is a giant mess since it doesn't appear to be possible to group the backlog by project/parent task/anything. Is there some better way to set that up so we can actuall...

Issues have some idiosyncrasies that may make you want to use tasks instead. If you do, you could create a project that everyone's permitted to create tasks in, and then those tasks can be variously "groomed" and moved even to other projects. You're sort of re-creating issue queues this way, but the...

How can I put the approval status of a task on an agile card? I tried just adding the field of "Current Approval Status Name," but nothing shows on the card. Is there any way to do this? A potential work-around is to create a status of "Approval" and use that column instead, but with more complex ap...

I'm trying to move some of my work over to an agile flow (Kanban, specifically, although Scrum could be the approach), but I'm running into an issue with subtask visibility. If a "story" (parent task) is moved into the board (or iteration, in Scrum), its child tasks are not, and there is no indicati...