Currently JCMA can't migrate any comments, description, custom fields beyond 32767 character limit. And fails such entities with logs

Truncated text "xxxxx -..." to cloud limit of 32767 chars

But the pre-flight checks for JCMA don't show any such errors. 

And the user has to find out after seeing the error that they need to follow "CommentBodyCharacterLimitExceededException: No message" or "The entered text is too long. It exceeds the allowed limit of 32,767 characters.." error message in JCMA. While it would be ideal if JCMA can handle the limit in a better way as requested at MIG-1356: Better Handle comments,descriptions greater >32767 chars. The pre-flight checks should atleast show all entities impacted by this limit before the migration. 

This feature request is to request improvement in current pre-flight checks to capture this limit.