My main problem with current inability to split user stories to tasks is that our stories are usually span over multiple product components and have to be implemented by different developers, usually geographically distant one from another. Typical example for "As user I can view a list of that and that" user story will involve changes in GUI module, communication module, server and client modules.
We need a way to split a single story to a smaller tasks (probably per component), to assign the whole story and the specific tasks to different owners and to track the progress of each task, so the overall progress of user story will be deducted from progress of it's tasks.
Another vote for this feature.
My main problem with current inability to split user stories to tasks is that our stories are usually span over multiple product components and have to be implemented by different developers, usually geographically distant one from another. Typical example for "As user I can view a list of that and that" user story will involve changes in GUI module, communication module, server and client modules.
We need a way to split a single story to a smaller tasks (probably per component), to assign the whole story and the specific tasks to different owners and to track the progress of each task, so the overall progress of user story will be deducted from progress of it's tasks.