Include the Project filter to restrict that to a project(s) and for displaying sub-tasks your filter should contain a way to include the sub-tasks returned by the epics labeled as Expedite. Don't change the sub-filter for now, first of all, your board should contain issues to sub-tasks which is not happening by looking at JQL you have. When you're ready to clone that epic (with its tasks and task sub-tasks), run that filter (by going to your project, clicking on "view all issues and filters", and clicking on the filter you just saved). You'll now see the epics and tasks in that epic. You won't see sub-tasks but they're cloned automatically with each task. David Cabeza Feb 27, 2020. My problem was that I changed a story to an epic. By associating the epic with the stories, they appeared with the word "unlabeled". I solved it by opening the epic and writing in a field called "Epic name" because I never found a function called "Edit epic". Tatjana Špoljar Nov 05, 2021. These would be the exact steps to achieve your need: Create a new select list custom field with the option "Automatically created", adding it to the create screen of your Epics and Tasks. Create a scheduled rule to create the Epic you need and set the Epic with the option "Automatically created" in the custom field you created: Create another Mar 17, 2022. Sub-tasks would not become stories, they're sub-tasks of the issue, and the issue is still there, and Epics can have sub-tasks, so there's no need to do anything. Jira doesn't delete issues during actions other than delete or bulk-delete. Moving the story to an epic doesn't delete anything. Can you go to the standard issue view of . Stories can. When a story that's in a sprint is converted to an Epic, it should be removed from the sprint. Epics don't show up in backlog view (they have their own side panel) so if a story is converted to an epic while part of a sprint, you don't see it as part of the sprint until the sprint is started when it shows up on the sprint board. In few words, there are components and epics which are today not modifiable in terms of labels. Epics are attached to their corresponding component and cannot be moved to another comp. And we want to keep this organisation. But when a user creates an issue in a specific epic, and realized he should have assigned the issue to another epic, the Select a story (or group of stories) to be moved. Click Move in the Bulk Actions menu. A drop-down menu will appear with a list of available destination projects. Choose a project, then click Apply. To move stories between projects via drag and drop in a Workspace, simply click on a story and drag it to the desired panel within another project. Dec 21, 2018. Also, please note that "Epic link" field is only available for issues which are added to epics in the epic view by clicking on the "plus" sign. If you have a sub-task added to an epic it will never show the epic link in the issue view of itself because the relationship between sub-task and epic is that of parent-child relationship Hi, This works with Automation. I have did this and worked (jira cloud version). Here are the steps Created new text field "Parent Epic Name" to Story and Sub-Task screens. For Story, Copy Epic Link from Epic Issue to Story's "Parent Epic Name" field. For Sub-task, Copy "Parent Epic Name" from Parent Issue to Sub-task's "Parent Epic Name" field.

jira change task to epic