-
Bug
-
Resolution: Fixed
-
Low
-
None
-
JCMA - 1.9.7, CCMA - 3.5.0
-
Severity 3 - Minor
-
1
Issue Summary
When starting a migration on a valid site, that gets deactivated during the migration causes the app migration payloads to have
jiraClientKey=unknown,
confluenceClientKey=unknown,
Steps to Reproduce
- Link a valid site to a CMA
- Create a migration that has an app migration stage
- Start a long running migration with app migration steps
- Deactivate site before app migration stage
Expected Results
App migration should not start in the server and listener-triggered message should not be sent.
Actual Results
The listener-triggered event is sent with
{
cloudAppKey=com.mycompany.appkey,
transferId=<uuid>,
migrationDetails={migrationId=<uuid>,
migrationScopeId=<uuid>,
name=Test App Migration A,
createdAt=1688522974000,
jiraClientKey=unknown,
confluenceClientKey=unknown,
cloudUrl=https://mycompany.atlassian.net},
eventType=listener-triggered,
messageId=<uuid>
}
Workaround
Payloads that do not have a valid clientKey should be ignored.
- is blocked by
-
CME-4118 Failed to load
Form Name |
---|
This has been fixed. In the event there's no client key (for Jira and Confluence) the migration won't be triggered and an error will be thrown.