I want to make a field required for one screen only.

[Md. Abrarul Huda]

I am using Default Field Configuration on multiple screens. When I'm trying to make a field required. It is also showing required on screens that it's not even available on. Can I make a field required on just one screen if I'm using the same field on multiple screens?

[Hans Polder _Devoteam_ · Accepted solution]

@Md. Abrarul Huda ,

Yes, this is possible, however you would need to create a custom field configuration. Also, your mandatory field will be mandatory for (at least) the whole issue types life cycle, meaning that it will be mandatory during creation as well. Since you're saying that you 'only want it to be mandatory on one screen', could you maybe give a bit more context before proceeding?

So:

1. Is it OK for the field to be required throughout its entire lifecycle, as long as it only counts for ONE (or more, as desired) issue type?

2. Or, if it really is just one screen, what type of screen does this apply to and when do users see this screen?

[Md. Abrarul Huda]

Was trying to use the same scheme for multiple screens. I created a completely new scheme and flow for that particular screen and flow. Since a change to a field config was effecting all the screens.
Still to answer your question if you can give me a better solution:

1. The field will be required throughout the entire lifecycle.

2. Users use this screen to create a task. I'm using same screen for all issue types except for bugs.

[Hans Polder _Devoteam_]

@Md. Abrarul Huda ,

It's always good practice to try and reuse configuration across different projects. The more you customize, the harder it becomes to maintain it 😊

As the field is required throughout the entire lifecycle, then adjusting the field configuration setup is the best way to go. You can still use the same Screen, but the field configuration will need to differentiate on the issue type where you want this field to be mandatory.

Let's say, the issue type you want this field to be mandatory in, is 'Story'. But, in all other issue types you would want this field not to be mandatory (like Bugs, Tasks, etc). And this would count for your entire Jira instance. 

In that case, you can do the following:

1. Go to Jira Administration > Issues > "Field Configurations"
2. Click 'Copy' next to the 'Default Field Configuration' and give it a meaningful name
   
3. Go to Jira Administration > Issues > "Field configuration schemes"
   
4. Give the scheme a name:
   
5. Click the big button on the top right
   
6. Choose 'Story' to be using the newly created Field Configuration:
   

At this point, nothing has changed yet, as you simply created a copy of the Default Field Configuration. So, when you now open the custom Field Configuration you just linked (see the example link below), you can now find the field you want to make mandatory and configure it accordingly.

At this point, it still won't take effect, as the projects in your Jira environment are still using the System Default Field Configuration.

Go to a project where you want to make a change and go to Project Settings > Fields > Actions > Use a different scheme to select the new Field Configuration Scheme you created :)

[Nicolas Grossi · Accepted solution]

@Md. Abrarul Huda You might need to check the field configuration scheme and field configurations asociated to the screen.

HTH

Nicolas

[Md. Abrarul Huda]

Was trying to use the same scheme for multiple screens. I created a completely new scheme and flow for that particular screen and flow. Since a change to a field config was effecting all the screens.

Thanks for your help.