Hello,
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...
regards
Karl Noben
Technical tasks as you describe should not add business value, if they do they should be part of a story.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.