No to disrespect, @John M Funk , but I disagree -- a little.
In fact, @Josreny Botardo, if you have a compelling use case, you can use Structure for Jira to create that "structure." Although, you probably want to create a custom issue type for that second subtask and a custom link type for linking that second "subtask" to the parent subtask.
However, John is right in that deviating from the expected Epic > Story > Subtask hierarchy in Jira is something you need to think about carefully. There are many built-in Jira features that will ignore this unexpected hierarchy.
I know this is confusing, but you can do this if you want to — and I know many companies that do this (or things like this). In fact, Structure was created due to a Jira enhancement request from someone asking for subtasks of subtasks in Jira, and Atlassian said, "no - we aren't going to do this."
Full disclosure: I work for the company that makes Structure.
Hope this helps,
Picking up on behalf of my colleague @Dave Rosenlund _Tempo_, here's the documentation on the feature that would allow you to build such a structure, but our Solutions Team (firstname.lastname@example.org) would be happy to work you through more specific examples.
Hope this helps,
👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events