-
Bug
-
Resolution: Fixed
-
Low
-
None
-
JCMA - 1.11.0
-
2
-
Severity 2 - Major
-
6
Issue Summary
The Migrations API for getting the status of a task always returns progress “0” or “100” even though the migration in JCMA’s UI reports it accurately.
This is reproducible on Data Center: (yes) / (no)
Steps to Reproduce
- Create a project on Jira DC (UI or REST API - regardless)
- Create a migration and run it following the ritual described here: Migrate Jira or # Confluence from on-premises to cloud using APIs
- Invoke repeatedly the status API with a similar request:
curl --location 'https://api.atlassian.com/migrations/public/v1/jobs/3acbd842-1f9a-428c-ab04-0e0e115d547c/tasks/0000018e-8ab0-2a47-9503-89f2b99cc9e6/status' \ --header 'Authorization: Basic XXXXXX=' \ --header 'Cookie: XXXXXXXXX' \ --data ''
Expected Results
The API response “progress” value should accurately reflect the one observed in Jira’s UI
Actual Results
The progress while the task is in “IN_PROGRESS” state never changes.
The progress is always "0" while the task is running:
{
"data": {
"status": "IN_PROGRESS",
"message": "Migration is in progress",
"details":
,
"progress": 0
},
"links": {}
}
Response when the task is complete:
{
"data": {
"status": "FINISHED",
"outcome": "SUCCESS",
"details":
,
"progress": 100
},
"links": {}
}
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
Form Name |
---|
https://developer.atlassian.com/platform/migration-api/guides/progress-details-examples/