Jira Story Vs Task Vs Epic

To my project manager friends, before you create an issue on Jira, make sure you understand what story or task or epic stands for. When any of these is misused, it can lead to a lot of issues in the future.

Epic, as its name implies, is An epic captures a large body of work. It is essentially a large user story that can be broken down into a number of smaller stories. It may take several sprints to complete an epic.

Epics are used as functional classifications (verticals) of our product, it makes more sense if we need to do some kind of measurements... Epics, in this case, will live as long the project exists.

Story is a kind of work that directly or indirectly affects our end-user experience.

Task is a kind of work that is purely technical, mostly NFRs, deployments, optimisation, code level, configs, etc ...

There is no true technical difference between a Story or a Task in JIRA Agile. But there could a semantic difference in that a Story could be about something of value to users, whereas a Task could be something of value to the team.