Wondering if there's been a change to the JQL for a current Sprint?
I've used this query for a while and lately it's telling me:
"Your project and sprint selection are invalid"
Query -
project = XX AND issuetype in (Bug, Story) AND Sprint in openSprints() ORDER BY created DESC
It looks like the query still returns the bugs & stories for a current sprint. If it is, why am I getting that error in the query?
Hello @Bud Herz
I am not getting that error with the same JQL.
Can you provide a screen image that shows the JQL and the error?
Can you double check the project Type, finding that information on the View All Projects page under the Projects menu?
Thank you for that additional information.
I see the same results as you; the JQL using Advanced Search is fine but when I then switch to Basic search I see the error.
I rarely work with the Basic search. 99.9999% of the time I'm using Advanced search and entering JQL directly. I do notice that if I start in Basic search and add the Sprint field then it doesn't give me the option to select from the sprint-related functions.
I assume that has something to do with the = (equals) specification and it being invalid to use sprint=openSprints()
If I select multiple individual sprints, run the filter, then switch to Advanced, I see that it translates to sprint in (x, y), but it doesn't seem to be able to translate sprint in openSprints() into a form that can be handled by Basic search.
I have no idea if this is a change from previous functionality.
Since you have a paid subscriptions I suggest you open a support case with Atlassian directly to ask about this. And it would be great if you report back here what you learn.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the quick reply.
Our Jira defaults to the Basic view so that's the only way I stumbled across this.
If I get around to it I'll open a ticket with them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm facing this issue right now, it was not the case till last week. Any updates on this
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the Atlassian community.
Are you on a paid subscription? If so I recommend that you ask your Jira Admins to open a support ticket about this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.