Issue Summary

When a Database has views that have Filters using any "Jira issue details" type of field inside a Filter Group, it may fail to display the results if accessed directly.

If accessing the link to the view directly or simply refreshing the browser while on said view, instead of seeing the rows, it will display a "No matching entries found" message.

This seems similar to a previous bug reported via this community post, but now (instead of with "Page link" fields) it seems specific to "Jira Issue details" fields within "Filter groups".

Steps to Reproduce

1. Create a Database, add a "Jira Issue" and a "Jira Issue details" field (for example, Status).
2. Create a new view for this database and add a filter.
3. Add a "filter group" and include the "Jira issue details" field on it, filtering by any value (For example, "contains" > To Do").
4. Save the filter/view.
5. Add some data to ensure some items match the criteria on the new view.
6. Refresh the browser while viewing the new view OR access the view through the view link. 

Expected Results

Database will display the same set of results.

Actual Results

Database displays a "No matching entries found" message, which only goes away if accessing a different view (e.g. main view with all records) before going back to the new view.

Workaround

Currently, the only workarounds are either navigating between views to refresh the records or adjusting the View's filters to avoid "Filter group" with "Jira Issue details" fields (when applicable).