Hi, This works with Automation. I have did this and worked (jira cloud version). Here are the steps Created new text field "Parent Epic Name" to Story and Sub-Task screens. For Story, Copy Epic Link from Epic Issue to Story's "Parent Epic Name" field. For Sub-task, Copy "Parent Epic Name" from Parent Issue to Sub-task's "Parent Epic Name" field.Jira Software Server and Data Center; JSWSERVER-25075; Make it easy to convert between Initiative, Epic, Story and Task/Subtask I must be doing something fundamentally wrong but this simple query does not work in JIRA JQL: issuetype = Epic. In search it works withount any problem, showing me all my epics and if I change to. issuetype != Epic. again it works showing me all non-epic issues.
We refer to this as a roll-up. These dates automatically update as those of the child issues change, but are overridden by any manually set dates. If your timeline is using these rolled-up dates, you’ll see an arrow icon when you hover on the schedule bars: In order to roll up dates: parent issues can’t have a start and/or end date set.
Hi all, Our Jira issues are structured like this: Epic -- User Story -- Tasks. There's (typically) 1 Epic per release. We use 1 User Story per 1 webpage that we're updating, then we do 1 Task per each stakeholder (ex: developer, QA, UAT; story points are recorded here).
One to create the 2 epics and the following two to make tasks for each of those epics. Just create the first Epic, and save that issue off in a variable from the { {createdIssue}} smart value: Then create the first Task under that Epic, and use the saved variable to set the "Epic Link" field. Tarang Apr 13, 2020. If you made an Initiative as "parent task of Epics" then this will show up in the initiative under "Issue Links" -> "is parent task of". and will not be identified as "Child issues" that "parent link" refers to. So it depends where and how you created the Epic. If you created the Epic within the Initiative in Jira Portfolio I would think a simple configuration at the project level that allows for a story or task to inherit said fields during the create screen and then put a button on the create screen to say inherit from Epic that is greyed out until the Epic link is populated. It should allow you to re-inherit if the Epic link gets changed by just reimporting the UT50ZTa.