JQL Search filtering by Request Type is not returning all expected results

[Calvin Maxwell]

I have a JQL query I use in an api call to build a table of data based on a specific projects Jira tickets. It worked fine until very recently, when someone pointed out that it seemed like the data table did not contain all tickets.

my original query is: Project = pl and "Request Type" = "Submission (pl)"

For the month of September, this returns 5 total tickets. I'm expecting it to return about 3200 tickets. I know this since I did a query that filters to the right issuetype, then did "Request Type" not in (list of other request types under the same issuetype i want to filter out).

In the jira filter UI, if i slightly change the query to: Project = pl and "Request Type" = "Submission"

It visually returns the tickets I'm looking for, and the count at the bottom says 1-1000+, however when i click on the 1000+ at the bottom, it updates and says 1-50 of 5"

I can only get the tickets i want to show up through the Jira filter UI, not through the API. 

I added request type as a column in the jira filter UI to ensure all tickets have the "Submission" request type, and they do. Both the 5 tickets that are returned by the original query, and the 3200 tickets returned through the second query. I don't understand how the query of: Project = pl and "Request Type" = "Submission" Isn't just returning the tickets I'm looking for since they all have that exact request type.

I've tried replacing "Request Type" with cf[10010] since that's the custom field code and that returns the results I've already been getting. I also noticed that the request type name of 'submission' has an ID of 110, but searching by "Request Type" = "110" does not return anything. 

[Christian]

Hello Calvin

This is a peculiar issue. I don't know exactly what's wrong, but I have a trouble shooting step that may help you figure things out. Create an automation that logs the request ID of the Issue it is trigger on. Below is a screenshot of what it should look like:

Trigger this on an issue that appears properly in your query, then one that does not appear properly, and see if the IDs match.

My main theory for this is that somehow there are two request types that have the same name and icon in the Pl project. That could explain the inconsistent returns of your query. Again, just a theory, but this could help us get to the bottom of it.

Regards,

Christian 

[Calvin Maxwell]

Hi Christian,

Thank you for your reply and offering a solution I haven't tried yet.

I've just ran this automation for two tickets, one that shows up in the 5 for september, and one from the 3200 tickets i should be pulling with my jql request. They both have the exact same request ID of 110.