There are limitations with the native Jira export. If you are open for a marketplace app, you can try Excel Online Integration for Microsoft Office 365. It works for Office 365 as well as for the Excel Desktop version. You simply select your issues and fields/columns to export directly in Jira. Also there is a real-time and a scheduled sync option.
You can use issue links to create your own hierarchy above and below Epics or infact at any level. To visualize the hierarchy based on the issue links, we have created an app to track the progress at each level, Agile Tools - Epic Tree, Links Tree and Time in Status . Key features of Links Hierarchy: Hierarchy upto 10 levels deep
When creating a new Epic, the Epic Name custom field is a short name field used to identify the Epic. By default it is available only to Epic Issue Type. It is intended to be used to label any issues that belong to the Epic. Starting in Jira Agile 6.2.2 or in any version of Jira Software, i f you add the Epic Link field as a column in your JIRA
Use Issues when: you want to track the piece of work across your Board (this piece of work will go through multiple phases, be accepted into the Sprint, and can be assigned to anyone). Use Epics when: you have large scopes of work, multiple moving parts, and need to see at a glance how complex something is.
There are three ways to export issues from Jira following this route: 3.1. Reactivate the Excel export option from the Jira menu. This option allows the Excel export option available from the Exports drop-down menu. Note, the "Excel document" that Jira will export is an HTML document that can be outdated at any moment.
Issue data (Jira format) payload for Send Web Request action; Limitations in team-managed projects for automation rules; Permissions required for Jira Cloud automation rules; Run Jira rules as another user; Test an automation rule using the Manual trigger; Transfer Jira automation rules from one user to another Displays a list of issues from Jira. This list can be static or dynamic, automatically updating as the status of your issues change in Jira. Status Report. The Status Report displays the progress of a Jira project and fix version in pie charts by status, priority, component, and issue type. The Status Report uses the Jira Chart macro, and is 1 answer. Bug is standard issue type and same as Task also. You can't move standard issue (bug) and other standard issue type task. You want to move this , you can convert issue type to sub-task using convert to sub-task option. With this you can mention task ID as parent for the sub-task.
Jira Cloud. Solution. When you move Epic issue from Team managed project to Company managed project, you will get prompt to move child issues along with Epic issue as well. Selecting this option will help to move Epic and child issues from Team managed project to Company managed project. Refer to the below screen recording.
i4cd.
  • 7l8tbhfv3v.pages.dev/61
  • 7l8tbhfv3v.pages.dev/940
  • 7l8tbhfv3v.pages.dev/519
  • 7l8tbhfv3v.pages.dev/31
  • 7l8tbhfv3v.pages.dev/240
  • 7l8tbhfv3v.pages.dev/277
  • 7l8tbhfv3v.pages.dev/632
  • 7l8tbhfv3v.pages.dev/637
  • 7l8tbhfv3v.pages.dev/400
  • 7l8tbhfv3v.pages.dev/519
  • 7l8tbhfv3v.pages.dev/727
  • 7l8tbhfv3v.pages.dev/566
  • 7l8tbhfv3v.pages.dev/688
  • 7l8tbhfv3v.pages.dev/378
  • 7l8tbhfv3v.pages.dev/625

    • jira convert issue to epic