All Issues of a Custom Issue Type are not showing up in search.

[Natausha]

We have a custom issue type "Meeting," when using search and setting Type to "Meeting" two issues show up. But adding the Assignee to a specific person in the search makes the search return 0 results. Also if I have everything set to all and just select the assignee as a specific person, none of the issues of this type show up. 

Why is this issues type not showing up in searches with the specific assignee?

Attached, is the search with only the issue type selected, and then with the issue type and one of the assignees selected. 

[Edited screen shots to show the Advanced query]

Using basic search and selecting only the Issue Type "Meeting" this is the result:

Now simply selecting the assignee of issue WR-78 (indicated the same in blue) I receive no results:

[Natausha · Accepted solution]

Issue Solved! 

The reply I got from the team was "First of all, we apologize if you faced some delay for this response, this ticket was internal escalated, given that, we needed more investigation to resolve. Actually had a problem in the database but the Senior Engineer found and was able to help us fix it."

[Yuliana Lopez]

why don´t appear some issue type in the JQL?

[Jack Brickey]

I don't understand your question. Can you please restate?

[Jack Brickey]

would you mind clicking on the "Advanced" link. it will show you the details of your JQL which will likely lead to the reason. Feel free to screenshot here if it isn't immediately obvious. Aside from that If you select the assignee in the dropdown in the Basic search where the assignee = one of the two issues in the first image it should return a result. Unless there is a bug but, while possible I expect it is unlikely.

[Natausha]

For clarity (Sorry I really thought the screenshots would be obvious) In the basic search I have selected the assignee from the first result in the first screen shot. (I used the blue censoring to indicate this assignee.) And it does not return a result as shown in the second screen shot. 

Same search again, but this time showing the Advanced query. Again the blue censoring is indicating the same assignee.

Basic search with only the issue type selected:

And now the exact same search, with the assignee also selected from the Assignee drop down:

Like wise, if I use basic search and only indicate this Assignee, and leave issue type and everything else set to "All" This particular issue does not show up in the list of issues assigned to this assignee. 

[Jack Brickey]

well if you are absolutely sure the assignee is the same in both "blue" cases then something is certainly amiss. I have never seen this fail. What I have seen is where there are multiple users w/ the same or nearly so name so while you think you have it right in fact it is referencing a different person that is not actually assigned an issue in the project. I expect that is unlikely and assuming it is not then I would highly recommend reaching out to Atlassian Support. It could be a recent update to your instance has compromised something.

[Natausha]

We only have 5 users and none of them have even similar names. I am 100% certain it is the same user. It also happens if I choose the assignee for the second result. I'll reach out to Atlassian Support. Thank you for your effort.

[Jack Brickey]

great. please update here if you get to the bottom of this or not. I'm very curious.

[Jack Brickey]

one other test for the curious...

can you go to the advanced and change "assignee in..." to "assignee = xxx"?

i expect the same error but one never knows.

[Natausha]

[Natausha]

Opened a ticket and linked back to this thread. I'll let you know when a solution is found. 

I've even gone and checked all of the issue type settings/schemes/workflows etc. Nothing seems out of place for this issue type. Other than it simply refuses to show up in searches...which definitely makes it a problem for my team. 

[Jack Brickey]

this is what the syntax looks like...

assignee = jack.brickey

[Natausha]

[Jack Brickey]

well i'm surely interested in knowing the root cause.

[Jack Brickey]

...one possible cause is an addon conflict. if you have any you could consider disabling likely candidates and retest.

[Natausha]

The only add on we have is AIO Reports. I don't see how it would cause this. And when I do run a report with AIO it actually does include these two issues correctly. 

So far my only response from Atlassian Support is that they were unable to recreate the problem, so it's not a bug, but they'll continue looking into it. 

[Natausha]

Issue Solved! 

The reply I got from the team was "First of all, we apologize if you faced some delay for this response, this ticket was internal escalated, given that, we needed more investigation to resolve. Actually had a problem in the database but the Senior Engineer found and was able to help us fix it."

[Jack Brickey]

awesome!!! you might want to extract the above reply into an "Answer" here and then accept it. Basically there was a true 'bug' in your instance that Atlassian had to address.