How to Filter Issues by Epic in Jira: A Comprehensive Guide

[#1]

Efficiently managing and tracking progress in Jira often requires sorting issues based on various criteria. One common requirement is to filter issues by their associated epic. This article provides a step-by-step guide on how to accomplish this, ensuring you can effectively manage your project's workflow.

• Click on “Issues” in the top menu.
• Choose the advanced JQL search modes
• In the search bar of the , type the query to filter issues by a specific epic. For example: "Epic Link" = EPIC-KEY, where EPIC-KEY is the identifier of your epic.
• You can refine the search by adding more criteria, such as status, assignee, or due dates. For instance, "Epic Link" = EPIC-KEY AND status = "In Progress".
• Once you have the desired results, you can save this search as a filter for future use.

Filter issues on the timeline

If you are working with the timeline view and want to streamline your work with epics, then check out some Planyway features.

As soon as Planyway visualizes all Jira issues by default, you can use Planyway filters to have only epics visible.

 

The other option is to group your timeline by epics which is super helpful when you want to see which issues are linked to certain epics.

[Alejandro Acevedo]

Hello, I am trying to obtain issues from Epics with due date major to 20 days after or major that this, but the filter is applying the filter to the issue due date instead of the epic due date. Do you know a form to apply this search.

project in (POR22987) AND due >= -20d AND (issuetype = Milestone OR issuetype = Task) AND (Summary ~ "Development" OR Summary ~ UAT OR Summary ~ "Go Live") ORDER BY parent DESC

[Mary from Planyway]

@Alejandro Acevedo Unfortunately, Jira’s native JQL does not directly support filtering by the epic's due date while applying it to the issues linked to that epic.

However, there are a couple of workarounds you could try:

1. Manually Set Epic Due Dates in Issue Filters

You can manually reference the due date of the epic in your filter. For instance, if the epic's due date is known, you can use it to filter issues linked to that epic. It would look something like this:

vbnet

"Epic Link" = EPIC-KEY AND due >= -20d AND (issuetype = Milestone OR issuetype = Task) AND (Summary ~ "Development" OR Summary ~ UAT OR Summary ~ "Go Live") ORDER BY parent DESC

Where EPIC-KEY refers to the specific epic.

2. Use a Jira App like ScriptRunner

If you need a more automated solution, tools like ScriptRunner allow advanced JQL searching, which can include queries based on the epic’s due date and its linked issues. You can create a custom JQL function that checks the epic due date and applies it to the child issues.

3. Custom Fields

If you have control over the Jira setup, you can create a custom field on linked issues (like tasks or milestones) that pulls the due date from the parent epic. This would make it easier to filter based on that date.

Unfortunately, Jira's standard JQL does not natively support linking filters based on the due date of the parent epic without third-party tools or custom workarounds.

Let me know if you want help setting up a specific solution!

[Maksim Beliaev]

I am not sure I can agree with the article since it promotes the deprecated way of doing this.

Atlassian deprecates Epic Link in favor of Parents to address SAF, I assume JQL should be reconsidered