On a side-project I'm working with someone else on at the moment, we're using Asana.
I'm the tech/coding part, whereas he has the domain knowledge, so we have a Workspace setup for the project, then have seperate projects within that - ie, at the moment we have a Front-End project, a Back-End project, a Phase 2 project and a Future project.
If it's a bug or something we want for launch it goes into Front or Back-End, for sometime after launch it's Phase 2 and a nice-to-have goes into Future - tasks get assigned to me when there's an action needed, once done I assign it back and once we're both happy then it's completed - we use the Comments to put notes down regarding ideas for how it should work/look etc. against the tasks.
One thing I like that Asana has recently got is sub-tasks, so you can break a task down into component tasks without cluttering your main Task list up.
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.
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)
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!
We're also using Asana for bug tracking at Endurance. Bugs get assigned into categories based on priority (P1, highest to p4, lowest).
Another great tool to use is Jing or Snagit to take a screenshot or short video of the bug, in action. Then it's a simple click to upload to Screencast and paste the unique URL for the screenshot into the bug. Much faster than taking screenshot, naming image, saving it, and attaching it.
Yep, I've had an account since not long after it was released, and I've seen some good updates come through since (sub-tasks being one of them) and the free account does fine for what I need (and if I'm ever in the position to need more then I'd be more than happy to pay for it)
I'm the tech/coding part, whereas he has the domain knowledge, so we have a Workspace setup for the project, then have seperate projects within that - ie, at the moment we have a Front-End project, a Back-End project, a Phase 2 project and a Future project.
If it's a bug or something we want for launch it goes into Front or Back-End, for sometime after launch it's Phase 2 and a nice-to-have goes into Future - tasks get assigned to me when there's an action needed, once done I assign it back and once we're both happy then it's completed - we use the Comments to put notes down regarding ideas for how it should work/look etc. against the tasks.
One thing I like that Asana has recently got is sub-tasks, so you can break a task down into component tasks without cluttering your main Task list up.
Works for us, may not for anyone else though :)