Issues with sprint history get incorrect format on the cloud database

Issue Summary

When migrating issues that have sprint history entries, JCMA will insert square brackets on the sprint id(s) list on the cloud database. This will cause some integrations to break due to the way the /rest/api/latest/issue/<issue-key>?expand=changelog returns the stored values.

Steps to Reproduce

1. Create a software project in Jira server;
2. Create one sprint and add issues to it;
3. Start the sprint;
4. Create a second sprint;
5. Close the first sprint and move the incomplete issues to the second sprint;
6. Close the second sprint;
7. Use JCMA to migrate the project in which you created the issues and sprints;
8. After migrating to the cloud, run the following endpoint to retrieve the history entries:

   • {{/rest/api/latest/issue/<issue-key>?expand=changelog}}

Expected Results

The sprint id entries should be displayed like the example below:

items": [
          {
            "field": "Sprint",
            "fieldtype": "custom",
            "fieldId": "customfield_<id>",
            "from": "1",
            "fromString": "Sprint 1",
            "to": "1, 2",
            "toString": "Sprint 1,Sprint 2"
          }
        ]

Actual Results

The sprint id entries are displayed within square brackets:

items": [
          {
            "field": "Sprint",
            "fieldtype": "custom",
            "fieldId": "customfield_<id>",
            "from": "[1]",
            "fromString": "Sprint 1",
            "to": "[1, 2]",
            "toString": "Sprint 1,Sprint 2"
          }
        ]

Workaround

Contact Migrations support.