⚡KNOWN ISSUE: Burndown and other charts not showing Burned items correctly after data migration from Server to Cloud via JCMA

[Danut M [StonikByte]]

Symptoms

After migrating Jira projects from Jira Server to Jira Cloud via Jira Cloud Migration Assistant (JCMA) the gadgets show zero Burned story points.

For example, trying to generate a Release Burndown Chart based on a filter that returns the migrated issues, will show a flat zero Burned line.

‌

If you manually reopen the issue and move it back to Done, it will properly reflect in the Burned line.

Cause

The cause is a bug in the Jira Cloud Migration Assistant (JCMA), more exactly in the migrated issue history.

Our app uses the issue change log (history) in order to determine the issue state (status, estimate, etc) along the time in order to be able to generate the lines in the chart.

The Jira Cloud Migration Assistant (JCMA) does not map correctly the id of the statuses from the issue history during the migration.
In the migrated issue history the status name appears as "DONE", but its id in history change event, which is not visible in Jira GUI, now matches the id of another status from the Jira Cloud instance that is not a "category-done" (green-colored) status.

To confirm this, open a migrated issue, go to its History tab and look at the event in which the issue was moved to “DONE”. The “DONE” status is not green-colored as it is expected to be, which mean that it is not” seen” as a category-done status by the app.

‌

Workaround

The workaround would be to bulk change the issues that were DONE before the migration and to re-transition them to the DONE status. Unfortunately this will make them all to appear as being resolved today in the release burndown chart, but at least the chart will display correct data from now on.

Resolution

There is no fix. This is a bug/limitation in the data migration process of the Jira Cloud Migration Assistant (JCMA) from Atlassian.