How to structure the EPIC, Story, Task and sub-task hierarchy with Design, API and FE requirements?

[Nischal Sharma]

I think it is quite a common problem where people find it challenging to organize the issue types into a hierarchy on JIRA. From all the research I did, I found out that a story should not exceed a sprint.

Typically in my projects, a medium-sized feature takes 3 sprints to get completed. 1 sprint for Design, 1 for the API team and finally 1 for the front-end team. From what I understand each of the 3, i.e API, Design and FE are supposed to be tasks but JIRA doesn't offer the Story to task hierarchy and even if it did it would be wrong in my case because the story would then go on for longer than a sprint.

I was unable to find any useful information on how to structure API, frontend and design tickets and how to associate them with the story. 

Any insights would be deeply appreciated.