Requiring fields is generally managed in through the Field Configuration associated to that issue type in the Field Configuration Scheme used by the project. In the Field Configuration a field can be set to Required or Optional. There are other ways a field might be made required (through advanced workflows, or third party products), but Field Configurations is the basic method used.
Field Configurations and Field Configuration Schemes are another resource (like Screens and Workflows) that might be shared between projects, so you need to assess the impact of changing them.
Similarly, fields are added to Screens that are compiled into Screen Schemes, and Screen Schemes get mapped to issue types in Issue Type Screen Schemes. All of those also may be shared between projects, so again you have to assess the impact of your changes.
You'll have to review the Project Settings for the projects you want to affect to see which Issue Type Screen Schemes and/or Field Configuration Schemes are in use. If they are using ones that are shared with other projects you'll have to figure out which path is easier for you to follow; modifications of screens and associated schemes or modification for field configurations and associated schemes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.