So if I understand this correctly we can make our own configuration for our fields, and assign that config to our projects in order to make certain fields mandatory without impacting other projects that do not use this configuration.
It's all basically a combination of fields, screens and schemes so yes, you can make field configuration schemes
Try to get acquainted with custom field contexts as well
To avoid confusion I suggest each issue type has the same required fields regardless of project you use it in
It looks like you're new here. Sign in or register to get started.
