Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

The following search returns absolutely nothing:

isaccepted:yes closed:no

This probably isn't proper behavior.

While I don't like the 'standard' behavior, searching for answers that aren't closed returns a list of questions that are not closed:

is:answer closed:no

Ideally, anything involving an answer would take the 'closed' status from the parent question, rather than having a 'flag priority' which returns unexpected results (especially returning no results at all, which is the worst possible behavior if there is no indication of what got broken).

For reasons unknown, the advanced search API returns things totally differently.

share|improve this question
Actually it returns three results on the main site – Shadow Wizard Oct 17 '13 at 6:30
@ShaWizDowArd Weird. All three from the same day too. What are the chances of that? Definitely not expected behavior at any rate... – jmac Oct 17 '13 at 6:31
Most likely a bug, marking those questions as accepted answers somehow. In general, you're "abusing" the poor search - isaccepted:yes is meant only for answers and closed:no is meant for questions. No results is actually the expected behavior in my opinion, but that's might be only me. – Shadow Wizard Oct 17 '13 at 6:33
It just struck me... if you're looking for non closed questions that got an accepted answer, proper query is hasaccepted:yes closed:no. – Shadow Wizard Oct 17 '13 at 6:35
What I'm actually looking for is answers to non-closed questions that are accepted. I want the search results to return answers. My original query was this: is:answer isaccepted:yes score:..3. If I use your workaround, I can only search for questions with a score less than 3, which could be useful as well I suppose, but really isn't the same thing, is it? – jmac Oct 17 '13 at 6:40
I see your point now, but it's not a bug - what you said about "anything involving an answer would take the 'closed' status from the parent question" might be a fine feature request. – Shadow Wizard Oct 17 '13 at 6:44
@ShaWizDowArd The fact that the search as-listed only shows 3 questions from the same date in October 2010 indicates that there is something funky going on with that search and it certainly is bugged. The fact that is:answer with closed:no only returns questions is not a bug and would be a feature request which I will make promptly. – jmac Oct 17 '13 at 6:46
Not really, this only expose a bug in the database raw data that somehow got messed (e.g. field containing some unexpected value). – Shadow Wizard Oct 17 '13 at 6:52
Sorry @Sha, I'm a bit lost. You are saying it is intended behavior for nothing to be returned if the isaccepted:yes/no and closed:yes/no flags are used together? That doesn't make much sense (since other combinations of answer-only and question-only tags return something). I would definitely label this a bug, though the database issue is likely a separate bug entirely. – jmac Oct 17 '13 at 6:55
OK, maybe it's on the edge... hopefully dev will pop by and end the confusion. :-) – Shadow Wizard Oct 17 '13 at 6:59

You must log in to answer this question.

Browse other questions tagged .