While server is being discontinued, Data Center will still be supported. You will still be able to run a single node Jira instance with a DC license which is essentially like running Server.

Use other plugins for reporting if you want to include sub-tasks in burndown. Alternatively, elevate your issue hierarchy. It sounds like your stories are too big if you're pointing sub-tasks.

FYI I would assume they will never fix this seeing that Jira server is being discontinued. I do have a problem with this. I suggest people start looking at hansoft as an alternative, it's much better.

Still no news on this?

Any update or workaround this issue? Need this chart badly.

Is there any update on the same ?

Yes, we are interested in this too. Another 9 years, maybe?

9 years later..... still not being considered? I just want to chime in that this is crucial as we want to break down a user story within a sprint to a more granular level to what needs to be done for that US. Example sub tasks for a US: create database, create table, populate table, create triggers, update code, unit test, progression testing, regression testing, etc.

Each sub tasks would then have hours estimate which are rolled up nicely into the user story. I don't want to have one estimate at the user story level only as that is way too broad. Now, if we have estimates in the sub-tasks, then we estimate in parent user story itself... Jira would show double!!!!

So, just to re-iterate, THIS IS CRUCIAL TO HAVE! Please make it happen. Thanks.

So does this mean that when we should ONLY be estimating and logging time to the story level? 

I am working with a team doing one week sprints. Sizing stories to be smaller than two or three days is not always easy to do upfront, so story burndown does not help much. The developers on the team are already in the habit of creating subtasks that approximate one day of effort as they pick up a story and closing subtasks as they work. It would be so very nice to be able to reflect this in a burndown that accounts for subtask completion. I don't really understand the hesitation to implement this. It has been a topic for a number of years and the Jira team takes the stance that it is not the way of Scrum. .. Subtasks are not actually the way of Scrum either, but they do exist in Jira. If Jira is going to have epic and story burndown, why not have task burndown for a sprint as well.

Indeed this is of high importance when you need to track the parent with large story points and not being able to complete with a sprint however the loss of estimate on its sub-task is not really displayed on the sprint burndown chart - that doesn't actually indicate the team velocity properly... Please consider to fix this bug..  Thanks!!