🌧️ Jira When To Use Epic

In Jira Software, issue hierarchy exists with Epics and Stories. Epics are used to track large pieces of work, and are broken down into smaller Stories. Portfolio for Jira lets you plan and track at each of these levels, with the Stories’ size (estimates) and progress rolling up to the Epic level. Sadly you cannot achieve the desired search using standard features on Jira, you must go for a third-party app instead. Using i.e. JQL Booster Pack (if you are on Server / DataCenter) you can type the following: 1) Find all task under a given Epic (i.e. EMEA-2459) "Epic Link" = EMEA-2459. 2) Find all subtasks under returned issues above The above worked for me on Jira cloud. BTW, I created another automation triggered on change of an epic's fixVersion to loop through all its issues and automatically update the fixVersion also. This covers the case where future epics get moved around in the roadmap as to when they will get done. As we’ve announced in Community, in company-managed project epics in Jira we’ll use Issue Color instead of Epic Color, and Summary instead of Epic Name. This is the current TMP behavior. Once we release this for company-managed projects in Jira, we encourage our partners to make a similar change. There is no deadline for it. Here's the JQL you'd use to find all epics in a project: issuetype = Epic AND project = PROJKEY So to extend this out to a REST API call, you can use the search endpoint: subtask 11. import 1 - Epics 1 + 2. import 2 - Stories 3+4 to Issue ID for Epic 1, and Story 5 to Issue ID for Epic 2. import 3 - subtasks 6+7 to parentID for story 3, subtasks 8+9 to parentID for story 4, subtasks 10+11 to parentID for story 5. I think this could be scripted to automate such a process and pull in the epic IssueId for the stories. Epics have Date ranges (start and end dates), but because epics can have child records — features — you can choose to have an epic's dates Calculate from features. If you select this (or if a workspace owner has set this as the Record dates default setting ), your epic's Start date will be the same as the earliest feature Start date and its Child issues of an Epic show in one list within the Epic. Jira automatically recognizes the parent/child relationship between the issues when you do this. If you don't want the parent/child relationship between the issues then use the Link Issue option. Generically linked issue appear within a separate list in the Epic. 5VNmLtC.

jira when to use epic