1. Make sure you have Epic Link field on Edit screen of Task Issue Type. 2. Filter all the Tasks that needs to be moved under specific Epic. 3. Bulk update the issues with Epic Link to target Epic Name and you would see all tasks moved under that Epic. Hope this helps. Jan 27, 2021. Technically, yes, but when you go to do it, you will find a warning not to. Heed that warning - it breaks a lot of things in interesting ways when Epics are not named "Epic". Atlassian do have an open and active development task on allowing it to be done, as Align needs it to be Feature instead of Epic as well, but until that is The scheme is used by a lot of projects, but the change does not affect other agile projects negatively. Try to open the issue type screen scheme, choose a screen for the BUG and try to add the Epic Link field. Maybe I did not understood correctly, but epic Link belongs to issue type epic only. You can create a bug as Issue in epic, then it Modify the default hierarchy levels. By default, Jira is set up with 3 levels of issue type hierarchy: Epic (level 1), Story (level 0) and Sub-Task (level -1). You can modify these levels to better reflect how your teams work. In jira default hierarchy is Epic > Story/Feature/Task/Bug > Subtask. In your case you want to have Epic > Feature > Story > task which is not possible in jira. As a workaround : You use the issue linking facility to create this kind of hierarchy . Create new Issue type ( Feature) ----- Using Linking ---> Epic --->Story -----> Task ( use as t6Z3M. The goal for my automation rule is for a user to edit the Epic Link field on a ticket and then it will automatically add a parent/child link between the Epic and the Story or Task. Here is the flow of my current build but I am having issue with choosing the right trigger. I would like it to trigger the rule when the issue field "Epic Link" has When label changes for an epic issue type, copy the values to the child issues (story/task/bug issue types) When label changes for a child issue type, copy the values to the grandchildren (subtask issue types) Rule #1 can trigger rule #2, so in the detail settings for Rule #2 you may enable the "Allow Rule Trigger" option to make this work. Like. And I can reorder sub-tasks on a task. But I can't re-order tasks underneath an epic. Each has a check box for an icon as opposed to a handle like a sub-task has. The two images I attach show the difference. The icon changes for a sub-task allowing the user to change the order. But the icons don't change for Tasks beneath an Epic. 3 answers. 1 ) Move the story to Epic. 2) Now, you have Epic with 20 sub-tasks, move the 20 sub-tasks using bulk udpate to "story" type. Before bulk moving sub-tasks make sure the "create" issue screen of the story type has the mandatory field "Epic Link" thus when moving the 20 sub-tasks you can fill the mandatory field "Epic Link" and mention If you need to run this automation only in one specific epic then you can change this query to: issuetype = Task and "Epic link" = TP-48 You must be a registered user to add a comment.

jira change epic to task