Hallo 

we just updated to Jira-Server v.7.13.1 and got this Problem > Advanced Search for Sprints is working but the BasicSearch doesn't show any Results.--

 Can you please reopen this issue or give us some Information for Bug-Fix?

Thanks!

To clarify the status, this Suggestion has now been resolved and will be available in an upcoming release of JIRA Agile.
edit: The fix version is 6.7.1 which is now available on JIRA Cloud and will be available shortly on JIRA Server.
edit: The Server release will be 6.7.2.

Kind regards,
Martin
Product Owner
JIRA Agile

It's also still happening in our instance: v6.3.12#6343-sha1:0d8f4aa

This is not fixed. I'm still having this problem.

Yeaaah , great news , indeed! I am waiting for it for a while

Great news, thank you!

marion.rosner, I can't give an exact date but the work is done and ready to ship.
As a guide JIRA Agile typically ships a new release every 2 weeks.

Kind regards,
Martin
JIRA Agile

Thanks for that, Martin. When will that be, exactly?

Cheers,

Marion.

This Suggestion has now been resolved and will be available in an upcoming release of JIRA Agile.

Kind regards,
Martin
JIRA Agile

Thanks for watching, voting and commenting on this issue.

marion.rosner there is an answer for how Atlassian uses JIRA.Atlassian.com at https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com

Regarding this issue, I'm pleased to be able to advise that the development is almost complete and that the feature will be available in an upcoming release of JIRA Agile. I will update the fix version for this issue at a time when the exact release version is known.

Kind regards,
Martin
JIRA Agile

Hi Atlassian,

PLEASE can we have an update on this? If I had had a story open for nearly 2 1/2 years, I'd have been fired for non-performance by now. A sprint is a basic unit of time and targets in Scrum, and to not have this field included in the basic search area is unbelievable.

Please provide an update.

One of your staff provided a brush-off answer nearly 1 1/2 years ago to say to use the advanced search. I know, let's just get rid of the basic search altogether, shall we?! I'm sure our managerial users will just love having to learn JQL or having to bug the devs or Scrum Master every single time they want to do a basic search. As it is, right now, they cannot do basic searches by sprint. This is unacceptable. How many people have to comment or vote for this to be done, before you will act on it? We pay you good money for basic features such as this. We should not have to pester you for simple functionality.

Thanks, on behalf of everyone here, and others who have not found this issue to vote on yet and are cursing you under their breath and considering moving to RallyDev or Trello,

Marion.

It would be nice to see this implemented. Like others have stated JQL is fine for technical users and admins, but a barrier for most regular users.

Highly agree; please fix

Please fix, this is a show stopper

Our non technical users can not use JQL. They are not able to do the searches they need which difficults their work. Please solve this issue as soon as possible.

Please fix--as mentioned above, Basic Filtering is the first and most powerful type of search for "non-power users". Using JQL is a deterrent for most nontechnical users.

Please fix this issue.

Please fix this issue.

Please fix this one

This is one of the Jira limitations that is causing frustration both within our development team and the client - can it be solved soon, please?

Please add support for Sprint in basic mode, it is a poor experience for a business user to be forced to JQL.

Thanks Peter for the workaround. Advanced search works fine. However I feel that some of attributes of this issue should be changed:

• issuetype: defect (to me this is clearly a defect and not a change request)
• priority: major (there is a good workaround, however Atlassian advertised the use of easy search queries that can be clicked together. Including the sprint seems like a logical think to add to building a query, if it does not work it raises a lot of confusion is perceived as a defect. Most of our users are not power users and should not expect to know Advanced query language, which would result in a large amount of user training etc., hence I feel this should be raised)

The workaround is to use Advanced search JQL.

I also just had one of our delivery teams report the same problem. Would be great if you can indicate a release.
In the meantime, are there any workaround suggestions?

When can we expect this in a release? Thx.