1 accepted. It sounds like you need to take this step so that your Portfolio Epic is available in the Parent Link field: Select> Products. In the menu on the left, select Advanced Roadmaps hierarchy configuration. Select or remove hierarchy levels you want to include in your plans. Select Save changes. Select the search field in the navigation bar and select View all issues. Click the Project filter, and select the project you want to migrate from. (If you're looking at the Advanced mode, you'll need to select Basic) In the top-right corner, select more () > Bulk change all. Story, 4, Story 4 summary, 1. Create an Issue ID field in your CSV. Assign unique numbers in that column to each issue. For the child issues, put the Issue ID value of the parent Epic in the Epic Link column for those child issues. When importing the data, again map that Epic Link column to the Epic Link field. John Nov 05, 2021. Epics and Features are higher level containers. User Stories and Tasks are more sub-level components. Epics can DIRECTLY be broken into User Stories/Tasks (aka backlog items) Epics IDEALLY need to be broken down into Features. Features can be broken down into User Stories / Tasks / Backlog Items. These tasks / stories are what fit into SPRINTS. As a work-around you can: Run a query to get your epic list. Export that result list. Grab just the keys, and convert them into comma-separated values (CSV) using a text editor. Paste the CSV epic list into your second query: "Epic Link" IN (yourCSVlist) AND labels = iPub ORDER BY "Epic Link", Key. Best regards, Steps (check out the attached for details) Trigger = Issue created [Note: this would be for one of the child issues.] Use a Lookup issues command to find the parent of the issue. Create a variable to store the key of the parent (e.g., { {myParent}}) Use Lookup issues commands to find each possible sibling. That is correct - subtasks are useless in Scrum planning and just waste space and make noise. A subtask always belongs to its parent, and that parent can have an Epic, which then implies that the sub-task is inside that Epic. But there's an oversight in that the subtasks don't actually inherit the information internally. Step 1: Log into your Jira account. From the WBS Gantt-Chart dropdown menu, select the project that you wish to export. If you’re using the cloud version, your Gantt charts are listed on the Gantt-Chart menu. Step 2: Click Data in the dropdown menu and select the type of export that you prefer. Step 3: A download dialog box will appear. Vay Nhanh Fast Money.

jira convert task to epic