Make Environment field required for one project?

[Richard Pawson]

I'm trying to make a field set to required for a single project, I've done this before for custom fields. I have made the project it's own field configuration scheme. It's associated to a screen. I think everything is set up correctly, or perhaps I'm skipping a step. 

So this global field "environment" associated to other projects, if I make it required, am I also making it required for other projects? I would like to prevent this from happening, I was under the impression that these fields are independent once a new Field Configuration Scheme is made (long story). 

[Carlos Garcia Navarro · Accepted solution]

Hi Richard,

You should be able to set Environment as mandatory for just one project by setting the field as required in the field configuration associated to that one project. E.g.:

1) Check the field configuration scheme for the project where you want the field mandatory. E.g, my project is Carlos classic project:

2) Click on the field config scheme and check the different 'field configuration' associated to the issue types. E.g., if I want to make 'environment' mandatory for issue type 'task', I'll check the field configuration linked to 'default'. Click on the field configuration for 'default':

3)Look for 'environment' and make it required. Make sure that this configuration field is shared by one project only (your project), otherwise you may make it mandatory for other projects:

4) Voila. Now it's mandatory for a task in 'Carlos Classic Project':

...but not for a task in 'Carlos Test Project':

Hope it helps,

Carlos

[Richard Pawson]

Thank you, Carlos! This worked. I was somehow neglecting to change the default in Step 2. Thanks so much!

[Carlos Garcia Navarro]

You're welcome, Richard. I'm glad this helped! :-)

[Teressa Reed]

How do you make a global field that exists in multiple projects required for only one project, e.g., Root Cause. When I follow the steps above, it updates all field configurations associated with the field.

[Richard Pawson]

Hi Teressa, 

   When following the steps above, double check to make sure you're editing the field configuration scheme for the one (single) project. When you're in the project's field configuration scheme, there should be a notation at the top saying 'Shared by 1 project' and it'll show you the project name if you hover over it.

A lot of people accidentally change the global/default scheme and all the field configurations get updated. That was my worry too!

[Teressa Reed]

Ah - I didn't realize you couldn't have any global field configs in the project's config scheme. That's what was throwing it off.

Thanks!