It allows you to have story points at both levels even at same time.
customer is demanding points and effort at sub task level plus points at story level for dev team motivation purposes even though they know its double counting
we need Atlassian to confirm when this enhanced functionality might become available
It allows you to do that if you want, and your customers can demand all they want, but if you estimate story points on sub-tasks, your burn-down charts and velocity all fail. So you shouldn't do it.
Atlassian have no intention of changing this at the moment (and hence, no intention of doing completion percentages)
Burn down appears to just reflect story level so should remain consistent as per stakeholders requirement but I will double check
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Apply agile practices
Transform how you manage your work with agile practices, including kanban and scrum frameworks.
Learning Path
Configure agile boards for Jira projects
Learn how to create and configure agile Jira boards so you can plan, prioritize, and estimate upcoming work.
Jira Essentials with Agile Mindset
Suitable for beginners, this live instructor-led full-day course will set up your whole team to understand how to use Jira with an agile methodology.