The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We are using only Story points to estimate Technical tasks.
Hi,
There's no way to do this at present. I'd recommend enabling 'Time Tracking' then using the Remaining Estimate but encoding story points, for example '1h' = 1 story point, '8h' = 8 story points. This will allow you to do what you're looking for if you apply 0h estimates to the parent stories.
Thanks,
Shaun
That's not a solution at all because it will affect plugins that measure time tracking like Tempo.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Greetings!
We have an existing feature request to reflect sub-task estimations on the burndown chart:
https://jira.atlassian.com/browse/GHS-6007
You might want to take a look at this one as well:
https://jira.atlassian.com/browse/GHS-5212
In the interim, you can configure a post-function in your workflow to set the remaining estimate to 0:
https://confluence.atlassian.com/display/JIRAKB/Set+Remaining+Estimate+to+0+on+post+function
I hope this info was helpful.
Cheers,
Jason | Atlassian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
"but encoding story points" in the above answer is confusing. Burndown chart should consider sub-tasks as well. Otherwise, there is no point in using sub-tasks. This is the major flaw in greenhopper.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We've solved this: during the sprint, the team updates Story Points field on parent issue by asking "how much points are their remaining?" resulting in points reduction or increase. This makes the chart burn down though the issue is still in progress :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.