Trying to figure how to configure Jira so that my hierarchy is Epics, Features, Stories, Tasks, Sub-Tasks. Just joined a new organization and it's currently set to Epics, Stories, Sub-Tasks. Looking into Jira it looks like I can add a feature issue type, but I don't know that I can configure it to have the child relationships story, task, sub-task.

After using for years the Epic Name as a label for tasks in Kanban boards f.ex., this is its de facto meaning, no other, a label in a card to identify the Epic there. If now someone changed that meaning, that is an undesirable change, a bug from this point of view. Now Epic Name has no meaning. From the articles:
As the name implies, epics usually represent a significant deliverable. In the backlog, you can filter by issues belonging to a single epic. Example: Character movement update; In this example, the epic encompasses the story of adding joystick support, as well other stories, tasks, and bugs in an overall initiative. It might look something like
You can send multiple issues to the top or bottom of the backlog. Select the issues while holding the 'Shift' or 'Ctrl' key, and then right-click > Top of Backlog or Bottom of Backlog. When you rank an issue that has sub-tasks, all of the sub-tasks are automatically moved with the issue.
So lets break this down: First we execute this rule whenever an issue is being transitioned. Next we check using a compare condition that the issue is a 'Sub-task'. We could have also used a JQL condition, but compare is a little faster to execute. The we branch of for the parent using the 'related issues' action.

Date ranges: Hover on an epic to view its date range. Drag its left and right edges to adjust the date range, or click the epic to open it and edit its details. Manage epics on the roadmap; Also, make sure that on Project settings > Issue types > Epic that the fields were added to the context fields. Regards, Angélica

Meet the powerful Epic Progress gadget. There is an Epic Progress gadget, and it’s available thanks to Dashboard Hub for Jira. This gadget displays the progression in the completion of a particular group of epics by different estimation statistics. Get the insights you need with a well-designed user interface and great customization.
Jira is well equipped to help you integrate Epics into your project planning phases with ease. Here is how you can create an Epic issue in Jira: Create a new issue. Select issue type as ‘Epic.’. Fill in the details such as epic name, description, and such. Click create.
For Sub-task, Copy "Parent Epic Name" from Parent Issue to Sub-task's "Parent Epic Name" field. What I did and didn't work: 1. create a new text field 'parent epic name' ) to Story and Sub-Task screens. 2. add an automation for when an issue is edited, the issue field parent epic name will be copied from the parent issue, field epic link.
Tip: All sub-tasks need to be complete in order to close a sprint. If a sub-task is still open, but the parent issue could justifiably be closed (say, if the sub-task for updating documentation is still open but the functionality is good to go), you can change the sub-task into an issue and close your sprint. I tested the rule in my test project and it works, i.e. the Epic-linked stories and tasks in an Epic are now additionally linked as "is Child of". I then moved the test Epic to Feature. The Epic links were removed, but the "is Child of" links are kept. Next step is to get a backup and then do the two steps project by project to. The feature’s Points field in Jira Align would sync with the Story Points field on the Jira epic. Note that Jira Align features (Jira epics) have story points in Jira Align that is a rollup of children stories LOE. Jira Align does not sync this field with Jira epics; it syncs the feature’s Points field which is a separate estimate.
Upcoming changes: 'epic-link' replaced with 'parent'. Currently, the epic-link connects issues from the base level (containing stories, bugs, tasks) to epics, and the parent-link connects epics to issues at higher levels for those who have Jira Software Cloud Premium. From October 2023, we'll be moving towards a single way of representing

Bulk Move the Tasks (Epic by Epic) into Sub-Tasks and select the corresponding Epic as the parent. Change the issue type of the Epics into Tasks (you can also do it in bulk) Link the Task to the Epic E1 with the Epic Link. I hope this helps. Tushar Mathur Oct 03, 2023. Thanks, yea eventually did this with some effort..

0WU1oI.
  • 5kinsnrbkq.pages.dev/340
  • 5kinsnrbkq.pages.dev/167
  • 5kinsnrbkq.pages.dev/185
  • 5kinsnrbkq.pages.dev/302
  • 5kinsnrbkq.pages.dev/4
  • 5kinsnrbkq.pages.dev/176
  • 5kinsnrbkq.pages.dev/151
  • 5kinsnrbkq.pages.dev/79

    • jira change epic to task