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.