Filter on dashboard adds 0d to AND statement

Berit Pearcy

When I click on my dashboard it gives an error saying it expected and AND OR statement but instead received 0d however when I update the algorithm, it continues adding back the 0d. Photo attached.

 

Jason U

Hi Berit,

That’s actually a known behavior in Atlassian Compass filters (and sometimes in advanced metrics expressions).
When you apply or edit a filter using date-based conditions — for example:

(created >= -52w AND created <= -8w)

Compass sometimes automatically appends 0d (meaning “0 days”) to normalize the date format internally.

It’s not an error in your logic — it’s the way the query parser rewrites relative time values.
However, if your dashboard formula isn’t handling that correctly, it can trigger the “expected AND/OR but received 0d” validation message you’re seeing.

✅ How to fix it temporarily

1. Edit the filter directly in Compass and remove the 0d at the end of the expression.
2. Re-save the filter — it should validate correctly.
3. If Compass re-inserts 0d automatically again, try rewriting the date section with parentheses, for example:
4. (created >= -52w) AND (created <= -8w)

or use an explicit date range like:

created >= "2024-01-01" AND created <= "2024-09-01"

🧩 Why this happens

The Compass filter syntax uses the same underlying time parser as other Atlassian analytics tools.
When it detects an incomplete duration (like -8w without a day value), it appends 0d to make it a full token — this can confuse the UI validator in dashboards but doesn’t affect data storage.