To clone an issue: Open an issue. Select ··· > Clone. Edit the Summary. Choose what to Include (if any). Select Clone. Keep in mind, the prefix Clone is automatically added to the Summary of a cloned issue. Your project admin can use Automation for Jira to remove the prefix in bulk. #Epics are a little wonky in #Jira. There's an epic name, an epic link, an epic status. Atlassian does Epics ever so differently than your average agile gu 1 accepted. You can remove/delete the linked issues from an issue. Go to an issue that contains links, and locate the Issue Links section. Hover your mouse over the link you wish to delete, and click the Delete ( trashcan) icon that appears. Kishore Kumar Gangavath. Be default, the Epic issue type will be associated with the Epic hierarchy level (level 1). You can add additional Jira issue types to associate them with the Epic level. To do this: Select the Jira issue types field on the Epic level. Select from the list of available issue types or use the search field. Select Save changes. To edit an issue: If you're in list view, hover over the issue and click the icon and select from the options. If you're in detail view, select the issue and update it in the issue details panel on the right. You can also select an issue and update it via keyboard shortcuts in either view. Use the j and k keys to select the previous/next issue I would think you could use the following. The first part covers the actual epic issue keys and the second covers the issues that are part of those Epics. Thank you Jack , I am awaiting the users exact JQL. So they are trying to exclude Epics that are part of an Initiative. The Initiative is the parent of the epic and used the field Parent link You can do that with the Bulk change function. Click on the 3 dots menu in the upper right next to the Export button. Then choose Bulk change and follow the steps. For the next question, issues are stored in the database and connected to a project. Issues can be viewed and interacted with on a board or a list. It shows the initiatives, but none of the epics or children. I created a plan for one of the dev teams, set the filter to the Team field. It shows the epics and stories, but not the initiatives (says "Issue without parent" above each epic). I expect in both plans I should be able to see the Initiative-Epic relationship in the top level view. If the issue (Story, Feature, Epic) has the sprint updated after the sprint is closed, then the reports in Jira Align may not accurately reflect the reports. Changed issues after the sprint is closed may not show in the report for that sprint. When preparing to close sprints in Jira, you should remove or split unfinished stories and adjust G5V7J.

jira remove issue from epic