epicsOf

The epicsOf function helps you find the epics associated with a specified set of issues.

It’s helpful for:

  • Providing a linkage between individual stories and the larger epics they contribute to

  • Identifying epics that are impacted by specific issues

Syntax and parameters

epicsOf(Subquery)

  • Subquery: A JQL query designed to select the issues for which associated epics are to be identified. This could be based on status, project, assignee, or any other relevant criteria.

Examples

  1. Finding epics related to overdue tasks:

    To understand which strategic initiatives are potentially at risk due to delays, you might use a query like:

    issueFunction in epicsOf("due <= now() AND resolution = Unresolved")

    This approach helps to highlight epics that contain overdue tasks, prompting a review of timelines or resources.

  2. Finding empty epics:

    To identify epics within a specific project with no child issues, you can use the epicsOf function in conjunction with other JQL criteria.

    You may try something like the example below, which may work depending on your use case.

    issueFunction not in epicsOf("project = <project name>") AND project = "<project name>" AND issueType = Epic

Jira Epic Link Field

Due to Atlassian’s recent deprecation of the Epic Link default Jira field, Enhanced Search has updated its functionality to align with new standards. This change means that renamed or customized Epic fields are no longer dynamically supported in Enhanced Search queries.

To keep your epic-related JQL functions (such as epicsOf and linkedIssuesOf) working smoothly, you need to ensure you’re using the Parent default Jira field. If you have renamed your Epic field, we recommend reverting to the default setup to ensure compatibility.

On this page