Issue with Filters

[Drishti Maharaj]

Hi,

I have a bit of an odd one and I am not 100% sure what is happening. 

The workflows between the 2 spaces are the exactly the same so same status is used.

Filter 1 - shows issues from January 2025, which is what I want.

project = "Space A"

and status = "CLOSED"

and created > startOfYear(-1)

and Satisfaction IS NOT empty

ORDER BY created ASC

Filter 2 - only changed the space, but it is only showing me issues from January 2026. It is NOT including 2025 and I cannot understand why. There are 2025 issues which have a satisfaction rating...

project = "Space N"

and status = "CLOSED"

and created > startOfYear(-1)

and Satisfaction IS NOT empty

ORDER BY created ASC

 
I do not know why the filter is doing this.

If anyone has any suggestions?

Thanks.

[Christos Markoulatos -Relational-]

Hi @Drishti Maharaj 

What i can think of for your second filter only shows 2026 issues is that the “Satisfaction” field isn’t actually the same field in both projects, You can create fields with the same display name, and your JQL may be referencing a different one in Space N. To confirm, open a 2025 issue in Space N that should have a rating and check the field ID, then update your filter to use that exact field (e.g., cf[12345] IS NOT EMPTY). If 2025 issues then appear, the issue was a field-name mismatch; if not, check whether CSAT was enabled later in Space N or if field context/permissions hide older responses.

Hope this helps!

[Drishti Maharaj]

Hi @Christos Markoulatos -Relational- - CSAT was always enabled in both projects since the start of the project. I also only have the default fields in the system and nothing else with the name satisfaction


I also am attached an issue from January 2025 in the same project where the satisfaction is filled in but not being picked up in the filter.
 

[Christos Markoulatos -Relational-]

Hi @Drishti Maharaj 

Since CSAT has been enabled from the start and you've confirmed there are no duplicate fields, this is indeed puzzling.

The only other thing i can think of is field context configuration. Even though both projects have the same "Satisfaction" field, they might be using different contexts, which could affect how data is queried.

To check this:

• Go to Settings → Issues → Custom fields
• Find the Satisfaction field
• Click the ⋯ menu → Contexts and default value
• Check if Space A and Space N are in different contexts

Also, try using an explicit date instead of the relative function:

project = "Space N" and status = "CLOSED" and created >= "2025-01-01" and Satisfaction IS NOT EMPTY ORDER BY created ASC

If the context looks fine and the explicit date doesn't help, this might be worth raising with Atlassian Support as it could be a data consistency issue on their end.

Let me know what you find!

[Drishti Maharaj]

It seems to be an issue with Atlassian. Had to log a support call with them and it appears the issue is related to the JQL configuration. They are currently investigating. 

[Christos Markoulatos -Relational-]

thanks @Drishti Maharaj for the update.