We are using only Story points to estimate Technical tasks.
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.
"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.
We have an existing feature request to reflect sub-task estimations on the burndown chart:
You might want to take a look at this one as well:
In the interim, you can configure a post-function in your workflow to set the remaining estimate to 0:
I hope this info was helpful.
Jason | Atlassian
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 :)
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events