Currently, the "Epic Label" field is only made "Required" in the Default Field Configuration. This logic needs to change to include any Field Configuration that is used for the Epic issue type in a project.

Testing Notes

Q: Does this logic also extend to recreation of the Epic Label field after it is deleted?
A: Yes. When the field is re-created it is again made Required.

Q: What if there is another field/scheme with a duplicate name? Are we referencing both by ID?
A: Field configurations are referenced by ID.