Issue Summary

Applying filter on Change Activity Log MasterLogs.asp page results in a Whoops error message

Whoops...

Something went wrong while displaying this page.
If you are stuck please contact the support desk.

Steps to Reproduce

1. Browse to Change Activity Log MasterLogs.asp page
2. Click Apply Filters button
3. Select Details, then choose contains option
4. Type in any search string e.g. role updated
5. Click Filter
6. Notice the Whoops error message

Expected Results

• Filtered results are displayed.

Actual Results

• A Whoops error message is displayed.
• The following logs are thrown in Splunk:

  2021-01-29 21:51:52 172.28.1.159 POST /MasterLogs FirstTime=True&Programs=364&Releases=66,71&FilterID=2188 443 10841 172.28.172.26 Mozilla/5.0+(Macintosh;+Intel+Mac+OS+X+10_15_7)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/88.0.4324.96+Safari/537.36 https://instance.jiraalign.com/MasterLogs?FirstTime=True&Programs=364&Releases=66,71&FilterID=2188 302 0 0 30276

  2021-01-29 21:51:52 172.28.1.159 GET /Error er=20238 443 10841 172.28.172.26 Mozilla/5.0+(Macintosh;+Intel+Mac+OS+X+10_15_7)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/88.0.4324.96+Safari/537.36 https://instance.jiraalign.com/MasterLogs?FirstTime=True&Programs=364&Releases=66,71&FilterID=2188 200 0 0 16

  { [-]
     ASP_function: OOFunctionsSql.SetRSParamsCursor
     correlationid: wYyvX64IvP4ykQYi4idCrQk0vMEuzlTsD3uHgaWOYlI=
     customer_db: instance
     error_description: Query timeout expired
     error_id: 20238
     error_number: -2147217871
     error_source: Microsoft SQL Server Native Client 11.0
     log_type: exception
     logfrom_location: Website-ASP
     sql: EXEC RPM_GET_AUDIT_LIST 10, 1,'And  Details   like N''%role%''And  Details   like N''%updated%'' AND CONVERT(date, AuditTimeStamp) <= ''1/29/2021 10:00:00 PM''', 'AuditTimeStamp DESC'
     timestamp: 2021-01-29T16:51:52.503000-05:00
     url: https://instance.jiraalign.com:443/MasterLogs.asp?FirstTime=True&Programs=364&Releases=66,71&FilterID=2188
     urlverb: POST
     user: 10841
     version: 10.86.0.13292
  }

Workaround

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