Issue Summary

Moving issues between projects with different field configurations causes fields to pop up in "update fields" if using different renderers. This is not mentioned in any documentation.

Steps to Reproduce

1. Create two new projects, by default these should use the default field configuration
2. Copy the default field configuration and create a new field config scheme and add it to that scheme
3. Edit the field configuration, and just change the renderer for some existing text field such that it isn't the same renderer, so use Wiki Style where Default Text is used in the default field config so there is a mismatch
4. Edit one of the projects and have it use the new field config scheme that contains the new copy of the default field configuration that you edited.
5. Create a new issue in the project using the default field config, ensure a value is specified for the field in question
6. Try to move that newly created issue to the other project using the modified field configuration
7. You'll be prompted to edit\verify the field content despite it not being required

Expected Results

Only fields with "required" on at least one of the projects would pop up in this screen as per outlined in the following KB article https://support.atlassian.com/jira-software-cloud/docs/move-an-issue/

Actual Results

Fields where the text renderer do not match between the two field configurations show up in this screen in addition to the fields that are required

Workaround

Change the field renderer for the field in one of the field configurations to match the field renderer in the other field configuration. This will prevent the field from showing up in the update fields screen.