Issue Summary

Team-managed (formerly next-gen) projects - Changing the issue type triggers the bulk edit action.

Steps to Reproduce

1. Create a team-managed (formerly next-gen) project.
2. Create two issue types with the same fields.
3. Create a new issue.
4. Try to change the new issue's issue type.

Expected Results

You can easily switch between two different issue types.

Actual Results

The bulk edit action is being triggered.

Notes

On company-managed (formerly classic) projects, we can switch between issues types if those issue types are part of the same workflow.
On team-managed (formerly next-gen) projects, we were able to switch between issue types since all issue types are connected to the same "workflow".

Workaround

Perform the bulk edit action.

Root cause:

The bulk move has been triggered due to the mismatch in the backend in terms of the number of required fields between the source and designated issue types. The mismatch happens due to a bug we had in the past which accidentally un-require a field which by default should be required.