Select the issues you want to migrate and hit Next. Select Move Issues and hit Next. On the Select destination projects and issue types screen, select where issues from your old project will go. If you’re moving from a team-managed project using epics, issues on this page will be grouped based on which epic they belong to. As my issue is to keep the EPIC LINK from the subtask's parent, here's what I add: At step 1, take subtask's parent's epic link and store it into a text custom field (I called it EpicLink(temp) as I'm not keeping it for long) as a step 3, run a new automation script on the tasks and update the epic link using the content of the EpicLink(temp Webhooks. A webhook is a user-defined callback over HTTPS. You can use Jira webhooks to notify your app or web application when certain events occur in Jira. For example, you might want to alert your remote application when an issue has been updated or when sprint has been started. Using a webhook to do this means that your remote application Create an Epic; Link the Epic to the Initiative A; Convert the Epic into an Initiative B; Expected Results. The Parent Link should be removed between the Epic and Initiative. Actual Results. The Parent Link is kept, causing to Portfolio understand that there is still an active link between the issues. Choose Tools > Bulk Change (top-right of issue search page) Select the Epic (s) you wish to edit and choose Edit Issues as the operation. Search on this page for Epic Status and change it back to In Progress or To Do. Follow the rest of the screens to bulk-edit. Refresh your board. ^ This second option worked when I tested it - let me know if . set your condition. Probably something like issue.epic=your epic. Then you add your script, where you recover alll the issues linked to the epic, and check their status. Create your logic so that if everithing is as it should be, you just change the status, using MutableIssue object. My team is using Jira Work Management as a project management tool and would like to see the tasks listed under their respective epics and subtasks under their respective tasks (in drop-downs) in the Timeline view. However, tasks and epics are currently not linked to each other in the Timeline view. They are listed as separate issues. 1. Create a new text field "Parent Epic Name" and add this field to Story and Sub-task screens. 2. Rule1: For Story > copy Epic Link from Epic issue to the Story's "Parent Epic Name" field. 3. Rule2: For Sub-task > copy "Parent Epic Name" from parent issue to Sub-task's "Parent Epic Name" field. Solution. Rule1 is for Bugs/Stories (standard 7. Trace requirements to JIRA issues. Most likely you and/or your development team spend a lot of time in JIRA. It's really easy to get from your Confluence requirement to your JIRA epic and vice versa. You can view all the JIRA links on any Confluence page, by clicking on the JIRA links button at the top of your saved page. 8. 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

jira convert issue to epic