-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
10.122.3
-
1
-
Severity 3 - Minor
-
No
-
None
Issue Summary
In the Story backlog if you have filter by a Kanban team with more than 100 stories breaks the view after the 100 row and generates error 500.
This is reproducible (yes)
Steps to Reproduce
- Have a Kanban team with more than 100 stories linked to it and to a PI
- Go to Story backlog and filter by Program + PI + your kanban team
- Scroll down and after the 100 rows it generates an error 500 and not shows other stories after it
Expected Results
After reaching row 100 load the rest of the stories
Actual Results
After reaching row 100 don't show the other stories from the kanaban team and throws error 500 with the following ASP and IIS error
2023-08-17 16:21:48 xxx.xx.xxx.xxx POST /AjaxFiles/AjaxPrioritize ActionType=57&ObjectID=4|19624|800a0cc1|Item_cannot_be_found_in_the_collection_corresponding_to_the_requested_name_or_ordinal. 443 200 xxx.xx.xxx.xxx Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/115.0.0.0+Safari/537.36 https://CUSTOMER.jiraalign.com/Prioritize?Programs=20&Releases=73&FilterID=319&SelectedTier2=95&SelectedView1=4 CUSTOMER.jiraalign.com 500 0 0 1927 host = PR-US-03-WEB-GHsc_status = 500source = C:\inetpub\logs\LogFiles\W3SVC3\u_ex230817.logsourcetype = ms:iis:auto
{ [-] ASP_function: Error.asp ErrorId: 7511 PageName: Backlog correlationid: H/J8O9TZF2A+Dqh137JqZxfXM9EtwrM6puSv6BGqi0s= customer_db: CUSTOMER 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: 19624 error_number: -2146825023 error_source: log_type: exception logfrom_location: Website-ASP timestamp: 2023-08-17T12:21:47.972000-04:00 url: https://CUSTOMER.jiraalign.com:443/AjaxFiles/AjaxPrioritize.asp?ActionType=57&ObjectID=4 urlverb: POST user: 200 version: 10.122.3.34697 } Show as raw text host = PR-US-03-WEB-GHsource = c:\log\CUSTOMER-ASP-20230817.logsourcetype = asp
Workaround
Currently there is no known workaround for this behavior.
- mentioned in
-
Page Loading...