-
Bug
-
Resolution: Fixed
-
High
-
10.68
-
3
-
Severity 2 - Major
-
Avengers - SCORP6
Issue Summary
This is a similar issue to Jiraalign-870, but we are now seeing issues with a smaller set of data. It appears that we are hitting a SQL time out while the export file is attempting to extract the data.
Steps to Reproduce
- Step 1 - User navigates to a program and PI feature or epic grid
- Step 2 - clicks more actions and exports the grid view
- Step 3 - Wait for the file to download
- Step 4 - Open the file
Expected Results
Seeking PDMs & QAs guidance on this bug
Actual Results
Corrupted file downloaded
It appears that we may also be running into a timeout on the backend before the export file has a chance to finish being generated. In this instance, the export was kicked off at 8:52:24 AM and we see the timeout on our backend logging that lines up with the export request.
A Sample backend timeout from a customer instance (customer info redacted): [view in JAC ticket]
Workaround
User have to use the backlog view export as a workaround (CSV File), but this doesn't provide to value to all customers because the list exported fields aren't identical between the two templates.
- is related to
-
JIRAALIGN-435 [JIRAALIGN-435] Query timeout expired when retrieving work item list
- Closed
-
JIRAALIGN-1469 [JIRAALIGN-1469] Unable to import work items
- Future Consideration
- resolves
-
ALIGNSP-2818 Loading...
-
PS-57239 Loading...