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...
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...
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