There's two parts to this. It's absolutely correct that a sub-task should not be assigned to an Epic. A sub-task belongs to a parent, and hence belong to an Epic via that. It's absolutely a howling bug or flaw in JIRA that sub-tasks do not behave as though they belong to the same Epic as their parent. Yes, a few times I've scripted a field that 1 - Create the new Epic you want to move your issues to. 2 - Navigate to your issue navigator and create a filter to return all the issues from the Epic you would like to move the issues from, using the Epic link field. Then, click on the three dots menu > Bulk update issues: 3 - Click to Edit issues > change Epic link, moving it to the Epic
Within JXL, enable the issue hierarchy. This is a one click action. You can now easily select the epics and their children (just like you would select cells or rows in Excel/Google Sheets), right-click them, and invoke the "bulk edit" process via the context menu. This is how this would look in action: (In the future, we may add a "move
Case 1: for an Epic, the Epic Name or Summary change. Case 2: for a Story or Task which are assigned to/removed from a parent Epic. There are actually two sub-cases: create and update. Case 3: for a Subtask which is a child of a Story or Task (please see Case 2 above).
If you plan to follow the concept of hierarchies, you need to change the use of tasks to sub-tasks, so the hierarchy in Jira would look like this; epic story sub-task. If you only plan to have tasks associated with your Story, you can do the following: When creating the task, locate the "Linked issue" field, insert the KEY of the Story and
as @Fazila Ashraf mentioned, you can have more than 3 levels of hierarchy (if you are on Jira Premium) - it's just that any additional levels of hierarchy need to be above epic. As you can rename your hierarchy levels, you can also model the system that you are looking for; you just have to keep in mind that there are certain semantics maix.
  • 1yb3umvjec.pages.dev/287
  • 1yb3umvjec.pages.dev/347
  • 1yb3umvjec.pages.dev/50
  • 1yb3umvjec.pages.dev/173
  • 1yb3umvjec.pages.dev/237
  • 1yb3umvjec.pages.dev/161
  • 1yb3umvjec.pages.dev/287
  • 1yb3umvjec.pages.dev/380
  • 1yb3umvjec.pages.dev/144

    • jira change epic to task