+1 to have the ability to use the subtasks back. We also estimate on the subtasks. Currently if you view a Version report, there is a link "View in Issue Navigator", but if you press that, you get all issues (including the subtasks). Which is what I would like to see reflected in the version report.

Old issue, but we just ran into the same problem as @Lee Naylor. Just upgraded to JIRA 6.4.11 with JIRA Agile 6.7.11 and now the version report is completely useless for us. The team uses Stories with sub-tasks, and put the estimates on the sub-tasks. These estimates are no longer reflected in the version report.

I would very much see an option (checkbox etc) to include sub-tasks in the version report.

Unfortunately we have updated our JIRA Agile plugin today without realizing this 'fix' was included and has made the Version report completely useless. Our team logs estimates and their time against subtasks and without having these included in the Version report there is no progress reflected.

I understand that some teams use subtasks and some use the higher level Stories, what I don't understand is why there isn't a solution that serves both user groups. On the regular Issue screen there is a check-box to include or exclude subtasks from the Time Tracking area, can this not be done for the Version report as well?

When this update there is no longer any area in Agile that predicts our completion date and we have had to revert back to the Classic Agile burn down chart.

Sure, we are way off-topic. It was customer comments like "I know what the different buttons do but how do I actually use JIRA?" that drove me to write Practical JIRA Administration

That's a fair comment. Can we leave the discussion here for this issue, and if you like continue further at a later point?

That's good, but the questions my customers ask are often at the next level up. What is missing is a page like the Estimating and Timetracking page that tells them what the approach is across all of JIRA Agile. So not just "how this page works" but "how GH is supposed to be used"

We are currently working on enhancing our reports offering. When we update the documentation to reflect the new enhanced reports, we will make sure to mention the lack of sub-tasks.

Yup, that's how I came to this issue. But the main Agile docs at https://confluence.atlassian.com/display/AGILE/JIRA+Agile+Documentation need something too for later reference

matt.doar, this was mentioned in the 6.3.6 Release Notes.

Michael, please would you make sure that this change is reflected in the documentation for JIRA Agile. How the estimates include subtasks (or not) and where subtasks are shown (or not) is a very common area of confusion for my clients. It would be great to have a page to refer them to about what is included in estimates and timetracking