Epics are used in agile software development to classify your user stories and lend a structure to your backlog. For example, if you're working on two-week sprints and you take on an integration between your product and a third-party application, it will likely take more than a single sprint to complete. This is where you can use epics. However, story points of stories are only calculated in an epic if I add them manually. If I add story points to a story, SP of the epic are calculated correctly: If I add story points to subtasks, they are calculated correctly by a different rule in the story BUT SP of the epic are not updated. I've been trying to experiment if/else block, but The main difference between the two is that user stories are small, lightweight requirements while epics are larger. The difference is size has implications on how product teams work with epics and stories respectively. It helps to think about epics and user stories in the same way as we think about rivers and streams: - A river is a natural How to create your first epic. Once you’ve logged in to your Jira account, navigate to the project in question and click the global Create button in the top toolbar. In the resulting window If the issue has a parent or Epic. If any of the issues in a sprint/version are unassigned. If all the stories in the Epic are resolved. That resolved sub-tasks of a specific type have a specific value set. Setting up the Related issues conditions. Select the related issue type: Sub-tasks. Parent. Stories (or other issues in this Epic) Epic Using Epic to represent a "Parent" seems a little odd, or maybe confusing with parent/child tickets already in use with Tasks/Subtasks. For us, Epics have serve more as a category to label each ticket / issue (e.g., a task for the eCommerce category of this project, a task for the Design phase of the project, etc.). Answer accepted. Projects only - the category is really called "project category", but we all shorten it. The Labels field can be used to categorize an epic. You can also create a custom field that can be called "Theme" with type plain text or labels type to categorize. Modify the project key accordingly and issue keys accordingly. If you are not using the Enhanced Search, then you will need to run the JQL Query like:-. (parentEpic in (11500, 11498) AND issuetype != Epic) The numbers 11500 and 11498 are the Epic issue ids. To get the Epic Ids, you will need to run the query below on the ScriptRunner console:-. gmxF.