Can I use context to limit the scope of a required field?

[Karen Clark]

I have a field called "Requested By" that is on a Field Configuration shared with 14 projects. The project that wants this field wants it to be required.

Is it okay to make this field required for that Field Configuration if I limit the field's context to one of those fourteen projects? If the field isn't on screens for or included in context of the thirteen other projects, it seems to me that it couldn't throw an error for being required without being on the screen.

This seems to work in my testing, but the approach isn't in Atlassian's documentation so I wanted to ask the community for advice.

[Petter Gonçalves]

Hello Karen,

Welcome to Atlassian Community!

You are correct in your presumption. Basically, make a field required will only be applicable if:

1 - The current Screen contains the required field

2 - The field context is applicable for that issue type and project

One thing to keep in mind is that if you Hide the mentioned field in the Field configuration and keep it as required, it will still return an error for the applicable issue types and projects for all screens the field is added to, although you will not be able to fill the field.

That being said, we recommend you to always set fields as optional in case you decide to hide them.

Let me know if you still have any questions.