-
Bug
-
Resolution: Fixed
-
High
-
10.122.3
-
2
-
Severity 2 - Major
-
No
Issue Summary
Loading story backlog beyond 100 items generates Internal Server Error. Observed in both current and New Nav
Steps to Reproduce
- Set Tier1 filter (or New Nav top navigation) with Team who has more than 100 stories in a single Sprint
- Open Story Backlog
- Select Sprint with > 100 Stories
- Scroll to the bottom of the page to trigger loading beyond item# 100
Expected Results
Story backlog displays beyond 100 items
Actual Results
Internal Server Error is generated
ASP Log reports:
ASP_function: Error.asp
ErrorId: 3170
PageName: Backlog
correlationid: IuicAhiNOud75gQBImjwvGYXlts+3LAQatB5pMQefHk=
customer_db: Alignsupport
error_aspcode:
error_aspdescription:
error_category: ADODB.Recordset
error_column: -1
error_description: Item cannot be found in the collection corresponding to the requested name or ordinal.
error_file: /AjaxFiles/AjaxPrioritize.asp
error_line: 19637
error_number: -2146825023
error_source:
log_type: exception
logfrom_location: Website-ASP
timestamp: 2023-08-15T12:36:29.945000-04:00
url: https://alignsupport.jiraalign.com:443/AjaxFiles/AjaxPrioritize.asp?ActionType=57&ObjectID=4
urlverb: POST
user: 661743
version: 10.122.3.34697
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- resolves
-
ALIGNSP-20740 Loading...
-
-