For convenience reasons, I use the hierarchical relation between stories and technical tasks to split "abstrast stories" in "particular stories". Those are implemented as technical tasks.
=> Is there a way to define some business value to those subtasks ? My aim is to use a value burndown graph not only based on value from stories, but also instead on value from tech tasks.
A workaround using custom defined fields would also be great, if the burndown chart is flexible enough to be based upon custom fields...
Every team in the world is unique, and so Atlassian believes that each and every team's best way of working needs to be molded to their unique circumstances – ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot