nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JQL "Sprint IN" logic broken

Adam Tiner_m61lrs

After the recent update to Atlassian's Cloud version of JIRA, several of my filters have ceased to function. I have made no changes to the criteria for these filters, but when I attempt to view them today, I am receiving the following message:

The operator 'in' is not supported by the 'sprint' field.

Is there a link to Release Notes that were produced by Atlassian in association with this change? I am sure that they would not deprecate existing features without an explanation or workaround - right?

Accepted answers

Adam Tiner_m61lrs

After further investigation, I have discovered that the issue was not caused by Atlassian - I owe them an apology. Sorry!

It appears that one of my admins decided to add another custom field named "Sprint" which was causing the conflict. Deleting this field resolved all of my issues.

I am updating my support ticket to instead recommend that they warn users about duplicate names for existing fields.

All comments

Adam Tiner_m61lrs

After further research, I have confirmed that this operator should be functioning for the sprint field. How do I contact someone at Atlassian about this?

"https://confluence.atlassian.com/jiracoreserver073/advanced-searching-functions-reference-861257222.html#Advancedsearching-functionsreference-openSprintsopenSprints()"

Sam Hall_h1otcf

Hi Adam,

I just tried on my Cloud instance and the following work OK for me:

sprint IN openSprints()

sprint IN closedSprints()

sprint IN futureSprints()

Are these the queries you are having problems with, or something different?

Sam Hall_h1otcf

p.s. The What's New page in the Atlassian Cloud documentation is where they currently publish details about changes/new features for Cloud products.

For example, recent JIRA Software Cloud updates are listed here: https://confluence.atlassian.com/cloud/what-s-new-686863216.html#What'sNew-jirasoftware

I haven't seen anything about these type of searches being depreciated.

Adam Tiner_m61lrs

Thanks for the response, Sam. I also appreciate you confirming that the operator/functions are still working for the Sprint field.

You are correct that those are the queries that I am attempting. Issue Description.PNG

I have opened a ticket with Atlassian for their assistance.

Sam Hall_h1otcf

OK. Your query looks valid to me and running a similar search on my own instance works, so it'll be interesting to see what Atlassian say on this.

Please let us know how it gets resolved, because it'll be helpful for others in community.

For the reference of others visiting this thread, the link to raise a support ticket with Atlassian is: https://support.atlassian.com/contact/

Adam Tiner_m61lrs

After further investigation, I have discovered that the issue was not caused by Atlassian - I owe them an apology. Sorry!

It appears that one of my admins decided to add another custom field named "Sprint" which was causing the conflict. Deleting this field resolved all of my issues.

I am updating my support ticket to instead recommend that they warn users about duplicate names for existing fields.

Ramya Krishnakumar

Thank you so much. saved us today!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software-cloud

jira-cloud

jql

sprint