[joycew]

Sounds like a great flow. We are using trello at the moment. A list each for current focus, bugs and new features for future dev. I can assign issue to someone in trello too but it's not very efficient and seeing lists of issues in a large board can be overwhelming.

We normally get together on Monday to sort these issues. Move urgent ones to the 'focus' list etc. But the main problem is that it's not very motivating to log issues and to solve them. It always looks like there are infinite amounts of work to do.

[kfullert]

Yes, I've had a quick look at Trello and it seems like I'm using Asana in a similar way - large lists are demotivating, this is why I like the sub-tasks way of working ...

Say we want a new feature to handle processing a file and generating metadata from it after upload - in this case we'd have a high-level task of "Generate metadata asynchronously on upload" then within that I can have sub-tasks like "Create Resque job on upload", "Generate metadata in Resque job", "Update model with metadata", "Mail user on completion" - this way the main task list isn't cluttered with too much detail, and when I'm in the actual task the list of things to concentrate on are fairly small (I like to break a task up into 5 or so discrete parts which seems about right to me)

[joycew]

I've tried Asana quickly before, seemed very similar to trello. But I really liked the inline ':' type to create a new section of issues, very intuitive and fast. Will have another go to see how well it fits our project.

Including all the sub tasks sounds great, means each time you complete a small task there is a sense of achievement. I'll try it out! Thanks!