How to make a custom field mandatory in 1 project

[Joao Borges]

Hi there

I am new to JIRA and would like to know how I can make a field mandatory in a single project and  not across all boards.

Unfortunately I tried to make a required field, and turned out that no one could create a ticket, due to this mandatory field that was not even showing on their boards.

Goal: Make this field below mandatory for only DEVELOPMENT project 

Thanks

----------------------------------------------------------------------------------------------------

Heres a screen shot of current filed:

[John Funk · Accepted solution]

Hi Joao,

You can do that through creating a different Field Configuration for that project. 

See this guide for assistance on how to do that:

https://confluence.atlassian.com/adminjiracloud/changing-a-field-configuration-844500798.html

[Joao Borges]

This is exactly where i made my field required that affected all boards.  So you are saying that i need to create a new field configuration for it ?

[John Funk]

You need a different field configuration for each project that has different required fields.

[Joao Borges]

Even if it is just one field ? i still have to create a field configuration for it. 

[John Funk]

Yes - and then just change that one field out of the dozens or hundreds you may have. 

[Joao Borges]

Interesting, so if try to add a 2nd field that goes into the same project, i could just add/edit into the previous one ( department one ) created 

[John Funk]

So it works like this - 

You have a Field Configuration Scheme.

Then inside the Scheme you can have multiple Field Configurations - each attached to different issue types. In other words, you can make some fields mandatory for Tasks but not for Stories. 

Then you attach the Scheme to the project. 

So if you want Field Q to be mandatory on project ABC, then you would create a Field Configuration Scheme for project ABC. I like to abbreviate so something like Project ABC FCS (where FCS is Field Configuration Scheme). It would include an FC (field configuration) that has field Q as mandatory.

Then I would attach Project ABC FCS to project ABC.

I would leave the existing scheme on the other projects where it is not mandatory. 

Does that help?

[Joao Borges]

A little bit. Thats one thing that i have been confused about. So lets pretend I create a custom field:

1. Custom field is created
2. Under Custom Field Context theres the following: Which i a can label anything under Configuration scheme Label and apply to any issue type/ if its global or to a specific project- correct ? Once this Scheme is created - I have to ADD A FIELD CONFIGURATION and linked this FIELD configuration Scheme to it , correct ? 

[John Funk]

Yes, that's correct.

[Joao Borges]

Thanks John, i will let you know if i have any more questions on it. 

[John Funk]

@Joao Borges  - Did you ever get this working for you? If so, can you click the Accept Answer so we can close this one out? Thanks!

[tjwood]

This isn't a solution if your company limits the entire company to only a handful of schemas. Too many simple Jira features are tied to administrator-level privileges, which is an impediment in massive companies.

[Malini]

Hello @johnfunk, Thank you for this clear explanation. I am utterly confused about field configuration vs field configuration scheme. Screens vs Screen schemes. I tried following the above steps for custom fields . When I created a custom field, I was prompted to associate a screen. When I tried to create a screen for my project, I was prompted to create field configuration.
Please can you give me an overall big picture ? Heirarchy of how all these (screens, fields, configurations and their respective schemes fit in) And also please share best practices when you have multiple projects.
Appreciate in advance.

[John Funk]

Hi Malini - Welcome to the Atlassian Community!

I am happy to help explain. Schemes are collections of multiple items under them.

For example, a screen scheme can be made up of multiple screens - one for create, one for edit, one for view. So you place your field on a screen which is a piece of the screen scheme.

Screen schemes are a little different because there is another higher level above that called Issue Type Screen Scheme. This allows you to have different screen schemes by issue type on a project. It is the Issue Type Screen Scheme that is attached to the project. 

Here is some more information:

https://support.atlassian.com/jira-cloud-administration/docs/manage-issue-type-screens/

And here is a helpful diagram:

https://confluence.atlassian.com/adminjiraserver/project-screens-schemes-and-fields-938847220.html