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.

Suggestion

JCMA preflight check should scan comments. If the comment status is not easily verified as public or private, it should flag this as a warning and provide a CSV report for users to download and review. A continue button can allow them to bypass and proceed anyway with a warning that JCMA may accidentally migrate public comments to private.