It would be great to add tasks to a story

Please please add this feature asap

We are currently solving this by making user stories be Features, which get points estimated. Only the product mgr can create stories. And stories are limited to things which a QA person can validate via the UI - a backend capability is not a Feature until someone can use it for something.

Then the subtasks to implement that Feature are created as Chores, which get 0 points. Developers can extract as many of those as they like. Again, no points for progress, only for finishing the Feature. That also encourages user stories to be small, lest the team work for days and get 0 points because they're still chipping away at an epic story.

There is no tracking of dependency, so we have to manually sort and remember that. It would be handy if stories could have interdependence, so that you could push the must-do-first tasks to the top and eventually close enough of them that you could finally Finish the actual top-level Feature that people actually are asking for.

+1. We have many stories that are too big in scope to be scheduled as a single task. Other stories require work to be completed by two or more different engineers on our team (that is, our engineers are not perfectly fungible).

Love that too - would keep us from sliming the backlog with many chores that serve the same purpose. Thing with those is that the tasks get quickly disconnected from the feature when you start them.

Please do not add this feature or make it an option. We are so happy to have a small tool to track stories and use note cards for the tasks. It is one of the best thinks about pivotal tracker to have small tool for all this without task and hour tracking.

About what klaas Prause said, maybe if this is implemented it can be turn on and off on a Project by Project basis

@Klass Prause: If you don't estimate and track tasks, how is your daily burndown chart useful or are your stories so small that they can be completed in a day?

Absolutely needed to have tasks under stories. Currently using http://scrumy.com (they have tasks under stories which can be dragged from To-Do, to in progress to Verify to Done) but wanting to switch to Pivotal 100%.

+10 (as in every member of our dev team.)

Please add this! :)

More +++. We currently use chores for tasks, but it's a pain if you have to move a whole group of them without having dependencies on the parent story.

We'd love this as well!

I think this would be a very helpful 'feature'. I realize that stories shouldn't be so big as to require a lot of 'to-dos' but in our work-flow they often do.

What frequently happens is the functionality is working but the UI needs improvement. Rather then restarting all the stories that require UI improvements, it seems this would be a happy medium.

Ideally, I would like 'Current' to be broken into two sections: Functionality and Design. Often this happens simultaneously, but not with all of our programmers : )

I'd love to have this feature. My solution so far: in the story description write out each task. As each is completed, edit the description and add a big (DONE) in front of the task. Easy!

I like Jonathan's take. We've done something similar, but indeed a simple "todo" list assigned to the stories would be awesome.

TODOs (tasks( would have a team member assigned and a checkbox to mark when "done"... I dont think even the scrum master should be nofitied when its done, they just mind more about the story itself.

Nice!

@danp I am very happy to hear that, keep with the awesome work! =D

Freaking awesome!!

Hey danp! Any news on this? We're very excited to see Tasks!

Do you happen to have an ETA on 'tasks'. We are evaluation a few different products. If Tracker had the concept of tasks, I think we would start using it immediately.

Any news? Acunote is driving our team crazy! Subtasks are the only feature that prevents us shifting back :(

Guys in the meantime here is how we're dealing with this. We make sure we break our stories to functional areas. So we really never have a story point of 8 anymore. You only see 2,3 and 5's in our project. We treat these smaller stories as tasks and label them with the name of the overarching story. So if there is a story of "Implement X functionality", we break that into three stories say "Write DB stored procs", "Code business rules", "Design user interface" and apply "Implement X functionality" label to all three . We also label each of those stories with the developer name so you can later search for developer labels and story labels. The labels are extremely powerful in Pivotal. Not missing the task level entries that much at the moment.