I think this is because JIRA reads this as "Retrieve sub-tasks for EPIC-123" (which is 0) as opposed to "Retrieve sub-tasks for stories in EPIC-123". I also thought about using issue in (linkedIssues(AAA-###) ) but I imagine this will involve programatically looping through all the stories that are returned in the above query.
I. Epic as a part of the product. Epic can represent a large, high-level yet functional unit of the product. For example, in ScrumDesk we have epics BACKLOG, PLAN, WORK, REPORTS. In the app, you can find parts, and modules, which are called the same way as a given epic. Top epics of the ScrumDesk product.
Step 2: Write a narrative explaining the epic. Next, you will write a short description of what you hope to achieve with the epic. This narrative should contain at least the following: 1. Who: the persona (in this case, the product manager) 2. What: your objective.
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.

An epic is a feature or functionality consisting of multiple building blocks and scenarios. Epics are derived from themes or initiatives and can be segmented into smaller pieces called user stories. An epic can span across multiple sprints, teams, and even projects. The theme, epic, and user stories share the same strategic goal at different

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.
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 you can type the following: a) Start with the actual issues (showing epic-link-column in results)
In order to include all issues with a specific label to a board, you just need not perform the following steps: - Navigate to your board > Click on the three dots icon > Board Settings > General > Click to Edit filter query. - Add the label to the query: Labels = "XYZ".
An epic is a large user story that can be broken down into smaller stories, and can span more than one project. Learn about epics in Jira Software Cloud.
These objectives can be tracked using some initiatives and agile themes. Epic vs. Story: The Verdict? Now, we discuss how you use the Jira epic vs story. When using stories that can fit within one iteration, use regular stories; Create an epic to unite several stories if you discover a connection between them How Stories, Epics, Themes, and Initiatives Benefit Your Team. Professionals highlight three common benefits of dividing development work into epics and stories and the rest chunks: 1. Allowing strategic decisions. A story point is a fundamental measurement unit in Agile. The metric estimates the effort needed to complete a certain backlog item.
An issue can have only one parent Epic that is recognized by Jira as the parent Epic. You can use the generic Link Issue function to link an issue to multiple Epics, but Jira will not recognize those additional Epics as "parents" of the issue.
Here are some of the ways that you could use an epic burndown chart: See how quickly your team is working through the epic. See how work added/removed during the sprint has affected your team's overall progress. Predict how many sprints it will take to complete the work for an epic, based on past sprints and changes during the sprints. Issues in Jira rarely exist in isolation. They often contain sub-tasks, are stories that are part of a larger epic, or are simply linked to other issues using certain relationships. This means that when using automation, actions often need to apply, not only to the source issue that triggered the rule, but also to any issues that are related to rw75Ro.
  • 3102zgk0p1.pages.dev/394
  • 3102zgk0p1.pages.dev/490
  • 3102zgk0p1.pages.dev/136
  • 3102zgk0p1.pages.dev/48
  • 3102zgk0p1.pages.dev/104
  • 3102zgk0p1.pages.dev/219
  • 3102zgk0p1.pages.dev/208
  • 3102zgk0p1.pages.dev/263

    • jira when to use epic