Value points on technical tasks


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...


Karl Noben

1 answer

This widget could not be displayed.

Technical tasks as you describe should not add business value, if they do they should be part of a story.

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted 7 hours ago in Statuspage

What are your best incident management tips and stories? #HugOps

 👋Community members! Downtime happens. And great incident response takes a village. Teams like Support, Dev, SRE, Ops, IT, and Marketing have to come together to resolve the problem while keep...

25 views 0 2
Join discussion

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you