-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
1
-
Issue Summary
The pre-migration report generated warnings for non-supported event types 18 and 19.
But the reporting is inconsistent.
This is reproducible on Data Center: (yes)
Steps to Reproduce
- The default notifications scheme will have Issue Archived and Issue Restored events.
- Since JCMA doesn't support these events migration, there will be pre-migration errors generated for these events.
- Multiple migrations from the same source (DC) to the cloud will generate more duplicates for these events for same projects
| Error category | Entity IDs or keys | Entity type | Entity name | Problem summary | Problem description | Next steps |
| Unsupported | <Project Key> | event | "18" | Custom event type | The Notification based on the event type "18" is not supported via migration(custom event issue). The value for this issue will not be migrated. | If you require this field value, use a csv import to update the issues post migration. |
Expected Results
For every migration plan, the error report should be unique and previous plan's report should not duplicated
Actual Results
All the previous plan's unsupported entries are duplicated in the new migration report.
Workaround
- Ensure there is no migration activity
- Take back-up of table, AO_6FF49D_PROJ_EXPORT_PREFLT
- The cached events are stored in this table and need to be cleared to avoid duplicate entries
- Delete the entries on the table, before starting the next migration.
DELETE FROM public."AO_6FF49D_PROJ_EXPORT_PREFLT"