Convert a subtask to an issue. Navigate to the subtask issue you would like to convert. Select more (•••) > Convert to Issue. In Step 1. Select Issue Type screen, select a new issue type (i.e. a standard issue type) and select Next. If the subtask's current status is not an allowed status for the new issue type, Step 2. That’s a great fit for an initiative, as no single epic could likely achieve that big of a goal. Within that initiative, there would be epics such as, “Decrease launch-phase fuel consumption by 1%,” “Increase launches per quarter from 3 to 4,” and “Turn all thermostats down from 71 to 69 degrees #Dadmode.”. At Atlassian: To allow various aspects of an issue to be assigned to different people. Navigate to an issue, and select more ( ••• ) > Create Sub-Task. Fill in the details as needed, and then click Create. Estimating issues in your backlog helps you to predict how long portions of the backlog might take to be delivered. If you estimate your issue will take weeks or months to finish, it should probably become an epic. Similarly, if your issue is too complex — if several sub-tasks are required to mark it as “done” — it’s better off as an epic. By splitting each task into easily-completed chunks of work, you’ll reduce technical debt and be able to In the issue there should be a "More" button. Click on the button and below "Convert to Sub-task" should be an option to "Move". You should be able to move the issue to story and choose what to do with fields that are present/required in one scheme and not the other. Thanks , i tried move and I could change it! Issues are the basic unit of work in Jira Software and come in various types: story, task, bug, etc. There are two additional issue types - epic and subtask - that can possess a hierarchical relationship with the aforementioned standard issue types. Let's run through some quick definitions. An epic is a large work item made up of subsidiary c3FdCx. First make sure to add the Epic issue type to your project. Project Settings -> Issue Types -> (* Actions) -> Edit Issue Types. Add the "Epic Link" field to your screens (not the name as you did above). Screens -> Default Screen -> Configure. Now go ahead and create a new Epic issue type. Once this is done you will be able to link the epic to Update the parent issue when a sub-task is updated; Comment on linked issues when an issue is resolved. Smarter smart-values! But wait there’s more! Smart-values got even smarter! You can now also easily get access to a parent or epic’s data via: {{issue.parent.fields.some field}} or {{issue.epic.fields.another field}} Follow the steps below to Link Epic to a Story. Click on “ Create ” (at top-middle) > Set Issue Type to “ Epic ” > Enter Epic Name and Summary > Click on “ Create ” >. Now, Go to a Story to link > Click on “ Show 6 more fields ” (right-side) > Select “ To Link to a Story ” in Epic Link field. How to Link Epic to a Story Condition: issue type is sub-task; Branch: for jql: key = {{issue.parent.Epic Link}} Action: the action you want to take; This will edit the Epic of the parent. Hope that is what you were after. Cheers, Nick Jira cloud. Diagnosis. The field 'Epic Link' on the child issue should be matched with the 'Epic Name' from its parent, but this mapping is not directly supported under Automation action. The available options are Copy from issue/Copy from parent/ Copy from Epic/ Copy from trigger issue, but these options are only for 'Epic link' not 'Epic Name Jira Software. Project and issue tracking. Jira Service Management. Service management and customer support. Jira Work Management. Manage any business project

jira convert issue to epic