To use it, just change the description of the epic to whichever string you choose, and it will first delete the subtasks/issues and then the epic itself. I don't think this is possible unfortunately. It's a bit of a chicken and egg problem with JIRA. The issue is that we recieve the 'issue deleted' event *after* the epic issue has already beenTo remove issues from the scope table: In the scope section of the plan, click the checkboxes of the issues you want to remove. Click the Bulk actions menu > Remove from plan. Save the changes by doing the following: Click Review changes. The 'Review changes' dialog will display, with all changes selected by default.
Indeed, Jira automation does not have a function to remove a component of a child issue (Stories, Sub-task, etc) when it gets removed in the parent issue (Epic or Parent task). We have the following feature request to get this function implemented on the rule triggers, so you would be able to use the Smart values to properly reference it in the
However, since Jira native fields can technically be unlocked by following the instructions from the KB article Unlock a locked Jira Software custom field, Jira admin users can edit the Epic Status options after manually unlocking this field from the Database, or can remove the issue type Epic from the configuration. If a Jira Admin user Enterprise. The old navigation will be removed from Jira Align in early 2024. Learn more about the upcoming changes. With the epics page, you can manage your epics at a central location. You can select which columns to display using the Columns Shown option. To sort the epics, click the column heading.