Note: running Jira Server 6.2 (I know, old) tl;dr Create task as regular, non-sub-task level, then do "convert to subtask". Epic Link will remain populated. I have tasks/stories with subtasks and just noticed some of those subtasks do have the "Epic Link" field populated, and so show in filters for "Epic Link = .", which is very nice. Jira’s Epics provide a powerful solution for managing complex software projects, and understanding how to use them can make all the difference. In this article, we’ll dive deep into the technical aspects of utilizing Epics in the Jira workflow, exploring the advanced features and Jira best practices that can streamline your software Flexible terminology will be a native Jira Software Data Center feature which means you are able to standardize terminology without the need for third-party applications. Admins can define naming conventions globally for every project and user, and can easily name epics and sprints the same for Jira Software (including advanced roadmaps) and Likewise, if you are moving child issue(s) and they have a linked epic, then you will get a warning to tell you that the child issues will lose their epic link. Example screenshots: (when moving epics without their children issues) (when moving children issues without their epic(s)) We are closing this ticket as resolved. Filter issues by "issueType = Epic AND labels != logWorkNotAllowed" then select only those which have a connected issue in sprint=XYZ. type = Epic AND (labels != logWorkNotAllowed OR labels IS EMPTY) AND issue IN epicsOf (' Sprint = XYZ ') >> This will return the Epics but not related issues. You can easyly save above queries as filters, give How to enable Jira cloud integration. Admins follow these steps to enable integration: From the sidebar, go to Admin and select the Integrations tab. In Jira, you'll have an option to Enable the integration. If a connection was made previously or if the integration was already enabled, you'll have the option to Manage the enabled integration. To add the Jira macro to a page: From the editor toolbar, choose Insert > Other Macros. Choose Jira from the Development category. Enter a filter or search for a Jira issue. Choose Insert . You can then publish your page to see the macro in action. Screenshot: Configuring the Jira Issues Macro to show a list of issues. 1. Start by displaying the Epic and select the Create Child Issue button. 2. After creating and saving the story, click on the "Add Epic" option in the issue key breadcrumbs. 3. After creating and saving the story, on the Backlog screen for you project drag the story from the issue list and drop it on the desired Epic displayed in the Epics pane. After saving you need to give your automation a name & click on the ‘Turn it on’ button: Now when you create a new ticket in this project with a name that starts “New Starter:” sub-tasks 89cxiLp.

jira convert ticket to epic