We use Epics as projects, however some projects have any number of sub-projects where designating them to a story or sub-issue would be counter-productive and designating an Epic to be a control Epic for subordinate Epics (projects) would be preferable.
An epic cannot have another epic linked to it using the Epic Link field, however two Epics can be linked using standard link features (i.e. relates to, duplicates,...)
Also Epics can have Subtasks in the same way a Story or Bug can... and also can have any Standard Issue type linked to it using the Epic Link special field.
Actually after toying with adding a test Epic, I answered my own question, and despite what Nic said, I found it is achievable. The way it appears achievable is that as an Epic is created, you can add issues to it in the form of stories. However after defining a story as if it were a new (sub-) project, you can then select the stories icon and change it to an Epic of its own. The new Epic stays subordinate to parent Epic but can now contain stories of its own.
The ability to structure stories in a nested fashion would be a great help. I think having just two levels (Epic > Story) is too limited to organize your backlog. It's getting too messy if you have lots of stories. This should be a standard feature. @Jira
In the meantime, I will be looking in workarounds like plugins.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
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