Select the issues while holding the 'Shift' or 'Ctrl' key, and then right-click > Top of Backlog or Bottom of Backlog. When you rank an issue that has sub-tasks, all of the sub-tasks are automatically moved with the issue. Sub-task issues can only be ranked in relation to their 'sibling' issues.
Just to add to John's answer: If you're open to solutions from the Atlassian Marketplace, you should be able to find apps there that can help with this. One app that comes to my mind is Issue Matrix for Jira, which extends the issue view. I myself work on an named JXL for Jira, which allows viewing sets of issues in an Excel/Google Sheets-style
I think you then create a rule with Issue transitioned as trigger, a Branch rule / related issues with the EPIC and below that a create issue action. See also the screenshot. And then of course expand with conditions. Does this point you in the right direction? Regards, Marco Click the Jira icon > Projects > then select the relevant project. Choose Settings > Screens. Click the > to expand the relevant screen scheme. Select the View issue screen. Add or remove the desired fields. Expand and collapse the screen scheme. The link to edit the View issue screen.
Here are the basic steps to create a new issue type: Go to the Jira administration menu and select "Issues". Under "Issue Types", click on "Add Issue Type". Give your new issue type a name and description that accurately reflects its purpose and function. Choose an icon to represent your new issue type. Configure any additional settings, such
Epics on your board and backlog will now display the epic’s Issue summary in their lozenge and on the epic panel. Additionally, the epic color on the board and backlog will now use the epic’s Issue color. These updates will also apply to the Epic link field in the issue view. Learn more about these changes.
leoP.
  • nr41f0l8m1.pages.dev/202
  • nr41f0l8m1.pages.dev/380
  • nr41f0l8m1.pages.dev/261
  • nr41f0l8m1.pages.dev/41
  • nr41f0l8m1.pages.dev/54
  • nr41f0l8m1.pages.dev/253
  • nr41f0l8m1.pages.dev/183
  • nr41f0l8m1.pages.dev/230
  • nr41f0l8m1.pages.dev/142

    • jira change issue to epic