Details
-
Bug
-
Resolution: Fixed
-
Low
-
None
-
None
-
None
-
Severity 3 - Minor
Description
Issue Summary
When calling
gateway.getCloudFeedback(transferId);
in Jira Cloud Migration Assistant, it always returns a HTTP 404.
This works in Confluence Cloud Migration Assistant as expected.
Steps to Reproduce
- Implement onStartAppMigration() and call gateway.getCloudFeedback(transferId);
Expected Results
If data is available then return feedback from app migration platform.
Actual Results
HTTP 404 is always returned.
The below exception is thrown in the atlassian-jira.log file:
2021-06-24 14:00:47,036 Caesium-1-2 WARN ServiceRunner [c.vendor.impl.MyPluginComponentImpl] getCloudFeedback error [INFO] [talledLocalContainer] com.atlassian.jira.migration.httpclient.exceptions.UnexpectedStatusCodeException: Received an unexpected status code; expected [200], but received 404: {"timestamp":"2021-06-24T04:00:47.054Z","status":404,"error":"Not Found","message":"No message available","path":"/feedback/b5bf0d34-68ac-39fb-b03e-6a199b115eec"}
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available