Issue Summary

In cases where a Folio contains a large number of work items, the RPM_GET_FOLIO_INFO_FOR_STORY and RPM_GET_FOLIO_INFO_FOR_FEATURE stored procedures are timing out because they're querying a large data set. The sproc does not have any filters in the where clause, which causes the whole table to be returned.

Steps to Reproduce

1. Use an instance with a large dataset of features and stories
2. Create and attempt to open a Folio that has all toggles enabled
3. Await the timeout Whoops error

Expected Results

The Folio opens to all work items in the selected Folio

Actual Results

The database is queried for the entire table, causing a timeout if there are too many items to index and return.

Workaround

Smaller number of work items will not be impacted by this.
No workaround available for tables with large number of work items