This question is in reference to Atlassian Documentation: Using the release page to check the progress of a version
We have decided to remove sub-tasks all together from the Version Report. This will be present in JIRA Agile 6.3.6.
If there is a legitimate use case for displaying sub-tasks on the Version Report, we will address it later. But by default we believe that most users do not benefit from sub-tasks being included.
Thanks for your patience.
JIRA Agile Team
But open opening a Version Report (aka Release Report?) in JIRA version 6.4.12 (per instructions here) and clicking, for example, 42 Issues to do, many of the issues then listed below are sub-tasks. How I can remove those sub-tasks from the list?
Agree that subtasks are of no interest on this level of information.
This said: if subtasks are removed, then their workload is not included either. This skews the Version report. This means that one would have to put the workload on subtask(s) level, and again on the maintask. This doesn't make sense either (and skews other reports).
Or is there another way to reconcile the need to have macro information in the version report, with having correct numbers (flagging/unflagging the '
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
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