You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
It sounds to me that your "tasks" are a type of sub-task. The rest of what I'm going to say is based on that assumption, so don't bother reading further if that assumption is wrong, just correct me!
Sub-tasks are a fragment of their parent story, they are not an issue in their own right. For that reason, they are not sprint items, and hence should not have a sprint estimate of their own. Their sprint estimates are a part of the estimate on the parent, not separated out.
For that reason, Jira does not put sprint estimates (default is Story points) on sub-tasks. Nor does it do anything with them if you do add them to sub-tasks - they will be ignored by sprint reporting because they're not sprint items, they are not accumulated up because the estimate should be put on the parent, not the fragment, and then the main part of Jira, the issue tracker that is not built for supporting Scrum won't see them as an accumulative field either, because Story points are a Scrum artefact (The issue tracker has accumulative fields for time estimates - the time-tracking "field" includes displays of "time on this issue with all the times on the sub-tasks added to it". But it doesn't do that for story points or other fields)
TLDR: don't put story points on sub-tasks. It does not work.