Atlassian recommends a top to bottom of Initiative, Epic, Story, subtask. But you can set this in Portfolio the way you want to with a different order or even additional levels. If you do not have Portfolio, then yes, Epic is the highest level issue available in Jira Software. You can't use Epics at this time without Software, (sorry Jira Core
For Jira Classic projects (Software or Service desk), these would be the steps: Click in the filter drop-down at the top of the page > Advanced Search; In the Issue navigator page, type a JQL query to return all the Epics and related issues you want to export. P.S: You can use the "Epic Link" field to select the issues related to a specific Epic
In order to create a subtask you need first get into the content of the parent Jira issue. For example in the following screen you have several options to create a subtask: You can click on Create subtask action and it will show up the Subtasks section with the default subtask type, where you can enter the summary.
List of Jira Issue Types: Jira Issue types are listed as follows: Story, Task, Bug, Epic, Service, Incident, Problem, Change, Post-incident review, Service request with approvals, and Claim. 1. Task: A task is an item or work that requires completion. Specific activities that shouldn’t take more than one working day are planned using tasks.
We believe using epics makes for better organization in your backlog and better planning for your agile teams. Epics help you deliver value sooner by keeping you focused on the big picture and out of the weeds. If you want a more contextual view of your epics and user stories in Jira, try Easy Agile TeamRhythm.