Making fields required in one project workspace should not make those fields required in other projects.

We are a company with multiple product divisions, with multiple projects in each division. While we do have some uniformity across projects at a high level, configuring our individual teams' processes is something we like to keep open for conversation among each of the teams. One of my projects would benefit greatly from making Resolved In Build a required field for Defects, but there are other projects that don't use that field so we can't make it required. I have plenty of other examples to provide if that would help.

Thanks for your consideration!