Technical Review Required for Complex JQL Logic in Rich Filter Dashboard (Incorrect Data Display)

[Hari Shankar]

Problem Description

Goal:
We need to troubleshoot and correct the JQL logic driving our Rich Filter dashboard. Currently, the dashboard is incorrectly pulling Q3 Epics into a view specifically configured for Q2.

The Problem:
We have a complex interaction between a Cascading Select List (Aspired Quarter), Date Fields (Planned/Actual Release), and an Automation-driven field (Spillover). Despite setting the static filter for 2026 Q2, the underlying query is not respecting the boundaries, likely due to operator precedence or the date range calculations.

Current JQL Context:

• Cascading Field: cascadeOption(2026, Q2)

• Date Logic: startOfMonth("+3M") and endOfMonth(-6M)

• Spillover Logic: Spillover = Yes AND "Spillover Quarter" in (Q2)

Observed Issue:
The dashboard URL reveals that Q3 tickets are appearing because the OR conditions are likely being evaluated independently of the final status and spillover filters.

Support Request:
I would like to schedule a call/screen-share session with a support engineer to:

1. Review the JQL nesting (parentheses) to ensure the AND conditions apply to the entire result set.

2. Validate the startOfMonth/endOfMonth logic to ensure it doesn't bleed into Q3.

3. Ensure the Cascading Select field is being queried correctly within the Rich Filter environment.

[Tomislav Tobijas]

Hi @Hari Shankar ,

When referring to 'Rich Filters,' are you using the app 'Rich Filters for Jira Dashboards' or something else?
If so, you could reach out to Appfire (app vendor) directly to help you troubleshoot this further 👀

Also, are you using rich filter controller (example from the linked app) or have you defined JQL directly for each gadget?

Cheers,
Tobi

[garrett_lessard]

Hi there,

You can definitely fix this in Jira or Rich Filters with the right JQL grouping. What you are running into is a classic AND/OR logic leak. When an OR branch lacks parentheses, it bypasses your Q2 constraints and lets Q3 epics sneak through.

Just a quick heads-up: I cannot jump on a live screen-share or call from here. However, if you paste your current JQL, including the Rich Filter static filter and any smart filter or controller logic, I can rewrite it with the correct nesting and date boundaries. If you prefer a live session, you will need to open a ticket with Appfire support. I can tell you exactly what to include so they can help you quickly.

Here is why your Q3 issues are showing up and how to fix it:

1. Why Q3 is showing up In JQL, AND takes priority over OR. For example, a query written like this: project = ABC AND status = Done OR labels = spillover

Is actually read by Jira as: (project = ABC AND status = Done) OR (labels = spillover)

If your query is split up like that, any issue in the spillover branch will show up on your board, even if it belongs to Q3, because the Q2 rules only apply to the first half.

1. The fix: Wrap your OR branches You need to isolate your Q2 rules and wrap your OR statements so they do not bleed into each other. The structure should look like this: (Your Q2 quarter or date rules) AND (Your eligibility rules, like normal issues OR spillover issues) AND (Common rules, like status or issue type)
2. Querying the cascading select list To query your cascading field accurately, use these patterns:

• For the parent only: "Aspired Quarter" = 2026
• For the parent and child together: "Aspired Quarter" in cascadeOption(2026, Q2) Make sure the field name and option values match your Jira setup exactly, including spaces and capitalization.

1. The relative date functions are likely drifting Functions like startOfMonth("+3M") and endOfMonth("-6M") shift based on the current day. They do not stay locked to Q2 2026. This means your date window changes over time and will eventually start pulling in Q3 data.

For a specific quarter dashboard, hardcoded dates are much safer: ("Planned Release" >= "2026-04-01" AND "Planned Release" <= "2026-06-30") OR ("Actual Release" >= "2026-04-01" AND "Actual Release" <= "2026-06-30")

1. Tighten the spillover rules If you want to include spillover issues, you have to explicitly tie them to Q2 so they cannot bypass the quarter filter. For example: ("Aspired Quarter" in cascadeOption(2026, Q2) OR (Spillover = Yes AND "Spillover Quarter" = Q2)) Then append your status and project constraints to the end of the query using an AND statement.

What to send me next: If you want me to write the exact JQL for you, reply with:

• The full JQL from your Rich Filter static filter and any smart filters.
• The exact names of your date fields.
• Whether an issue qualifies for the dashboard via the quarter field, the date fields, or both.

If you decide to go through Appfire support instead, send them the Rich Filter URL, your JQL, and a few examples of Q3 epic keys that are showing up incorrectly so they can diagnose it on a call.

Let me know if you have any other questions!

Garrett Lessard, Appfire Expert Services