This is indeed something that would really help us to see if we are on track to finish all of the work in a sprint.

Our stories are graded in Story points obviously but to encourage teamwork we create subtasks and put some hours on it. Team members use the swarming technique to finish the story so they pick up subtasks and log their work on these. This is not reflected in the burn-down so only after the complete story is done (after a couple of days) we know if we are on track or not...

This functionality is available on Jira Server so no idea why this was removed

I'm just starting to use Jira Cloud and I have a general feeling of putting a great step back...

I clearly understand why everyone is looking for this functionality. Sometime I also wish for this functionality. however, if we think in true agile/scrum spirit, we estimate user stories. we add sub-tasks to make it more granular, but they are very dependent of the story

We estimate stories using story points ( i understand there are many teams estimating in hours/days etc as well)

if we estimate sub tasks in story points, what is the point of estimating the story in the first place? if we need an ability to estimate sub tasks in story points, then the main story should not be estimated. having both is definitely going to make lot of confusion 

One of the creator of Scrum Jeff Sutherland himself stated that Estimating tasks will slow you down, don't do it. He also stated that best teams have small sorties and do no tasking. 
so split the stories into small chunks.

I can see the harsh reposes coming to this but hey, that is how scrum works.

Yes, we would very much like this ability. It would give us a much more realistic idea of how we are progressing towards Epic completion

This is absolutely required.

Estimating subtasks for a story is essential for many.  We work on one element (subtask) of the 'big picture' at a time (parent task/story).  Time spent is tracked.

When I'm asked for a 'date' for when I will deliver something 'story points' will not help me.  Time estimations will.

I don't know why anyone would come here and discuss not wanting an option like this. If you don't like it don't use it. It would be incredibly helpful for our workflow.

I see sub tasks not considered on burn down chart as a good thing. Estimation should be at the story/task level and not at sub task level. Sub-task is to describe the steps to deliver the value and there is option to record the time 

This would give a much more realistic view

Yes, I would like that feature too. 

This issue has been around for ages and seems to have been forgotten by the Jira business owner. Our team has moved on to other metric tools to follow sprint progress and estimation.

it's very important case to my command. Hope it'll be fixed asap