created field configuration and workflow specialized for project affecting all projects

[Carla Ann Rowland]

have custom fields that need to be required on specific issue type.

created field scheme and screens and workflow specific to and issue type; this is for a specific special project

 when applied it worked once then all of a sudden on different issues (in different project and scheme) started requiring those fields to be filled.

What did I miss?

[Nic Brough -Adaptavist-]

One of your admins has changed the field configuration for the project, making the fields required.

[Carla Ann Rowland]

The admin did set this up to give one project the proper permissions to have these fields required in their project only.  So why did the other projects impacted. The one project has special screen and its own field configuration and its own workflow as documented in Atlassian documentation.

[Nic Brough -Adaptavist-]

I suspect if you check the configuration for the projects, you will find they are using the same "Field configuration scheme" and/or the same "Field configurations".