Example workflow: Already in system: BAU Epic (label: BAU, due date: 31 July 2023) New issue created: Task 1 (label: BAU, due date: 21 July 2023). Automation Rule triggers upon creation: Checks for Epic label = BAU AND Epic due date month and year = Task 1 due date month and year. If both conditions are TRUE, add Epic link for BAU Epic to Task 1. The Edit Issue changes the Components field, selecting Copy Components from Epic issue, as I described earlier. Also for that edit, there is a checkbox for Add to existing values . Leave that checked if you want the epic's components added, and. Clear it if you want the epic's components to replace values in the children. Steps for Integrating Microsoft Excel to Jira. Here are the simple steps to start exporting data from Microsoft Excel to Jira: Step 1: Create a Microsoft Excel Spreadsheet. Step 2: Save Mircosoft Excel File/s as CSV. Step 3: Using the CSV Importer to Load Data from Excel to Jira. Epic -> 3. In Progress. Story -> 2. In Progress. Sub-task -> 1. In Progress; When the Sub-task is moved to 'In Progress' I would like the Story to then transition to 'In Progress' (easy, already done) AND also update the Epic into 'In Progress'. Can I create a rule to do this using Jira Automation? Go to issues > Search for issues. Enter this JQL into the advanced tab: issuetype = Epic and project = XYZ. Then hit the export button at the top right. Jack Brickey. Community Leader. Mar 29, 2018. and if you want all of the stories/tasks under the epics included in your export try this modified one. (issuetype = Epic or "Epic Link" is not If you have tedious duties and sometimes create the repetitive epics with subtasks in Jira with the same structure as me, you must have wondered how to automate this process. Issues at that standard level can have sub-tasks, but they can not contain issues at the same level. The "epic link" field makes it look like the Epic contains the stories, but it's not a parent/child relationship like issue-subtask is. To create an issue in an Epic in the main JIRA UI, create it via the usual "create issue" and fill in the 8. Create an acceptance criteria list in Jira. At the end of the day, the acceptance criteria list is nothing more than a DoD that is specific to every user story. To implement an acceptance criteria list in Jira, either create a new custom field or piggyback on the global DoD. With Checklist, you can add items directly at the issue level. Meantime, I have created Initiatives in Jira and was trying to link epics to the newly created Initiatives. If Jira allows creating an Inititive as a higher level in hierarchy above Epic, then there should be an easy way to link epics to a parent Initiative just like stories can be linked to a parent epic, without using Portfolio. 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. Rename a hierarchy level. To rename a level in your issue type hierarchy: Click the level name that you want to rename. w6vi.