[JIRAALIGN-2273] Expanding Epic Backlog logs out users -- and throws errors in the backend

Issue Summary

Expanding Epic Backlog logs out users – and throws errors in the backend

RPM_GET_BACKLOG_PAGINATION_DATA times out and throw ASP error

Steps to Reproduce

1. Browse to the Backlog page
2. Set Tier1 filter options and choose Programs with ~500 Epics or more
3. Click "+" (plus sign) to expand the Total Items list
4. Notice the user gets logged off
5. Notice the error in Splunk

   { [-]
   (...)
      customer_db: <CUSTOMER>
      error_description: Query timeout expired
      error_id: <ERROR_ID>
      error_number: -2147217871
      error_source: Microsoft SQL Server Native Client 11.0
      log_type: exception
      logfrom_location: Website-ASP
      sql: EXEC RPM_GET_BACKLOG_PAGINATION_DATA '','SET NOCOUNT ON;  DROP TABLE IF EXISTS #tPortfolioRankDisplay;  Select * from (  Select [TotalItemsCount]= COUNT(*) OVER() , 1 AS TypeVal, tReq.ItemSortType, tblRequests.ExternalKey,  tblRequests.Blocked,  ISNULL(tblRequests.Theme, tPTheme.ThemeID) as ThemeID,
   (...)
   

Expected Results

• The Total Itens list is expanded and the Backlog Epics are displayed.

Actual Results

• User gets logged off and SP timeout error is thrown in Splunk

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.