-
Bug
-
Resolution: Timed out
-
Medium
-
None
-
None
-
9
-
Severity 3 - Minor
-
3
Issue Summary
We fixed an issue where the entry in changeitem table would have null value for the newvalue or oldvalue column for status change entries. This was caused by Jira Cloud Migration Assistant not importing the status ID of statuses deleted on the Server instance.
The issue was fixed in https://jira.atlassian.com/browse/MIG-935 but the corruption for old entries still exists which causes problems like requestTypeId context parameter not being passed to connect add-ons.
Steps to Reproduce
The values are correct now for new migrations as it was fixed in https://jira.atlassian.com/browse/MIG-935.
But for old customers, corrupt values still exist which cause problems like this -> https://jira.atlassian.com/browse/JSDCLOUD-9788.
Expected Results
- There shouldn't be any corrupt entries inside the tables.
Actual Results
We can see entries with null value for newvalue or oldvalue column in changeitem for affected old migrated customers.
Workaround
We can update the corrupted entries for a single tenant if required.
Update any missing entry newvalue and oldvalue on the changeitem table with a dummy id or copy correct ids from the corresponding table on the server
- depended on by
-
JSDCLOUD-9788 requestTypeId context parameter is intermittently omitted
-
- Closed
-
- is addressed by
-
JSDM-788 Loading...