Click Project Settings > Issue Types. Ensure there is not a custom standard or sub-task issue type called "Epic" - you'll need to change its name or remove the issue type. Press "Add issue type" and select the Epic and create it. I would suggest avoiding using the "Epic" name at other issue type levels, see this note in the page you linked to:
After using for years the Epic Name as a label for tasks in Kanban boards f.ex., this is its de facto meaning, no other, a label in a card to identify the Epic there. If now someone changed that meaning, that is an undesirable change, a bug from this point of view. Now Epic Name has no meaning. From the articles:
That will give you the option to select a different Epic parent or unlink the issue from any parent. 2. In the Backlog screen expose the Epics panel. Drag and drop the issue from the issue list on the right onto a different Epic of the "Issues without epic" section of the Epics panel. (This works in Company Managed projects also.) Any of those could have children (Sub-tasks). Bringing in the parent brings in all of the children. Epics are different, and are normally a bigger chunk of work that would span sprints. For RW-24, if you really need the pieces brought into different sprints, change them into something other than sub-tasks using the move function to convert them. The epic status dashboard template displays the status of a specified Jira Align epic work item. You can use this dashboard as a presentation layer for status reporting to managers and executives, saving you the time needed to manually create status reports in presentation software. You can also modify the dashboard in Atlassian Analytics to Agile teams use epics to track larger sections of work composed of smaller tasks, bugs and user stories. Jira uses the suggested epic issue type to power other features in team-managed projects, like roadmaps and reports. To use these features, you must use the suggested Epic issue type (and avoid creating your own custom issue type called "Epic"). bPL3v0.
  • 612w654tde.pages.dev/398
  • 612w654tde.pages.dev/57
  • 612w654tde.pages.dev/15
  • 612w654tde.pages.dev/361
  • 612w654tde.pages.dev/144
  • 612w654tde.pages.dev/566
  • 612w654tde.pages.dev/414
  • 612w654tde.pages.dev/165

    • jira change epic to task