An Epic in Jira is a single goal or deliverable that is broken down into a group of related tasks that can be worked on independently. In this video, our Atl Deleted user Jul 11, 2018. Hi @Chethana Hashani, To be able to delete an issue in Jira you need to have the correct project permission to do so. Check out a similar question. You will need to set yourself the permission Delete Issues on the project's permission scheme. in the project settings. Hope this helps. If yes check that you: Have permission to transition issues in the project. You can use permission helper to confirm. Confirm what transition are available directly from issue view. Ensure there are no conditions needed to be met in the workflow that may be preventing you from transitioning the issue. Confirm with your project admin and server 1c) do you need them to remove the labels if someone accidentally tags them the wrong way? This can get really sticky, since you may affect quite a few tickets with these rules. 2) Initiatives are not a standard issue type to out-of-the-box Jira, and so JQL isn't easily able to 'see' initiatives and their relationships to the epics->tasks Answer accepted. Airbus Driver. Rising Star. Jun 16, 2021. When you delete the task, the subtasks associated with it are also deleted. You can delete the task by clicking on the task -> locate the three dots on the top right -> Delete. You need to have permissions to 'Delete Issues' in the permission scheme. Lynn Sheffield Jun 16, 2021. 2. Added the "insert JQL Query, issuetype = feature" function. 3. Added the "insert JQL Query, issuetype = epic" function. This would result in showing the Epic and having a "break" between the Epic and Feature level. The feature level now shows stories linked to it and no duplicated stories were added. 4 answers. You can also try a Clone Epic feature of the free app Epics Map for Jira provided by my team. As mentioned in your previous post you can clone Epics and all it's issues with our cloud app Deep Clone for Jira. Don't hesitate to get in touch with us at support@codefortynine.com if you have questions or feedback. The way to do that is to first create an artificial Issue ID field in your input data, and populate that with a unique value per issue. Example: Issue ID, Issue Type, Summary. 1, Epic, First Epic. 2, Story, First Issue. Then you use that unique Issue ID in the field where you want to create the link. For example if you want the above story to From the Object drop-down menu, select Story. From the Program Increment and Program drop-down menus, select the PI and program to which the stories belong. Select the check boxes of the stories you want to delete or click Check all to select all stories. Click Move to Recycle Bin, and then click Continue in the confirmation message. I've added the "add issues under epics" automation, which works fine. the problem is it now shows the stories under the epic, as well as, all the stores at the same level as the epic. so, the stories are under the same folder twice. :/ The server instance does not have this behavior, but also has an automation to remove dups. MZqh.