Issue Summary

Whenever a user tries to do a historical search for next-gen issues with a specific status/type/resolution, JQL returns incorrect results. 

status was "Done" -> won't return any next-gen issues
status was not "Done" -> will return all next-gen issues

Steps to Reproduce

1. Consider a Next-gen project
2. Try use historical search keywords like (WAS, WAS NOT IN, CHANGED ) in the JQL
3. JQL will either show all or none next-gen tickets (depending on whether NOT was used) instead of filtering as per the Historical search.

Expected Results

Should give the list of issues in the specific status during the mentioned time period.

Actual Results

JQL results either all or none next-gen tickets (depending on whether NOT was used)

Workaround

Next-gen projects define a custom schema for entities like status, type or resolution. Historical JQL searches don't support it. As a result for next-gen, it is required to pass entity id instead of name.

To find the id of a specific status/type/resolution, check its value on one of issues using GET rest/api/2/issue endpoint. Then use it in JQL:  status was IN (10002)