Steps. In Jira Product Discovery, select the idea you want to convert into a Jira epic. Click Delivery. Select Create a delivery ticket. Search for the Jira project where you want the issue to be created and then, select the issue type. Click Create. Now you can see the epic as a list on the delivery tab. Every time you create a new issue or 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. When you update the issue type from Epic to Initiative, the child issues from the Epics are not kept since it's not possible to make a relationship between Story/Tasks and Initiative Expected Results It would be great if when changing issue type from Epic to Initiative, Jira offers you the possibility to also convert the current child Story Jira comes with a default set of issue types, but these can be customized to fit the needs of your organization. The default issue types in Jira Software include: Epic: An Epic issue type in Jira is used to track and manage large pieces of work that can be broken down into smaller, more manageable pieces called stories. Epics are typically used With that said, I created my 1st automation rule that adds a parent/child Link Type (as automation for Jira currently isn’t supporting advanced issue linking past the Epic level) once the ‘Parent Link’ field is populated on an Epic. Next, I have a 2nd automation rule that I’m trying to configure following this logic: Jira smart values - JSON functions. The following smart values are available to convert issue fields into JSON format, when setting up a rule. This is usually used in advanced field editing and on the Send outgoing web request action. Check out how we use smart values in our Jira automation template library. In the case of versions, those are managed at project level so it makes no sense having a version that does not belong to the target project. But there is no problem with a story having an epic link from other project, if you want the epic to be in the same project you could clone the original epic and then bulk change epic links in you moved stories or something like that. When creating a new Epic, the Epic Name custom field is a short name field used to identify the Epic. By default it is available only to Epic Issue Type. It is intended to be used to label any issues that belong to the Epic. Starting in Jira Agile 6.2.2 or in any version of Jira Software, i f you add the Epic Link field as a column in your JIRA tSRrbHE.

jira convert issue to epic