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.
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
@Jack Graves [AC] first caught our eye with his incredible breakdown of what, in his opinion, can make or break a Jira software implementation. (Read his thoughts on this thread)! In this follow...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs