Issue Summary

JCMA may migrate comments that are public on Jira DC as internal due to the default behavior in JCMA 1.12.49+

The primary trigger appears to be due to the state of the comments in Jira DC. If the status is not clearly identified as either:

• {"internal":true}
• {"internal":false}

Then the default behavior will migrate the comments as internal.

Steps to Reproduce

(App integration may cause this behavior)

1. JSU automation to sync comments from Project A to Project B, may be saving records to the  database with a different state such as:
   1. {}
   2. NULL
2. Migrate JSM project from DC to Cloud using JCMA

Expected Results

JCMA should be able to correctly migrate comment status (private/public) based on Jira DC behavior.

Actual Results

JCMA will migrate these comments and set comments to private by default.

Workaround

If comments cannot be corrected proactively, users may rely on Jira Cloud REST API to update the comment status Post-Migration

• https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-comments/#api-rest-api-3-issue-issueidorkey-comment-id-put
• As part of request body, user must include the following to update comment status to public:

  • "properties":[{"key":"sd.public.comment","value":{"internal":false}}]