setting field permissions on a system field
Asked by donhames:

I need to make the system field Affects version required on some field configurations. It should be required on one set of screens but not on other screens.

Is this possible? If anyone has a suggested way to do this, I would greatly appreciate it if you shared your knowledge. I appreciate any help you can provide.


Answers:
author: Trudy Claspill
body: Hello [@donhames](/t5/user/viewprofilepage/user-id/5226196)

The Field Configuration can be used to set a system field to Required ++at all times++ for the projects to which the Field Configuration applies. You can't set the fields to Required only on specific screens.

Also note that Field Configurations apply only to Company Managed projects. If you are working with a Team Managed project setting a field to Required at all times is a different process.

Can you provide more information about your scenario and the problem you are trying to solve? Perhaps we can provide alternate solutions.

comments: author: donhames
body: Hi Trudy. Let me get more specific and see if that helps explain what I am trying to do.

We only use company-managed projects.

I have a Bug issue type that is used by hundreds of projects.

The create and view screens are the same for all projects.

The default field configuration has the Affects version configured for all the projects.

I need to have five projects that require the Affects version.

The other projects will remain as just being on the screen but not replied to.

I can't figure out how to have the Affects version system field appear twice in the field configuration, one for the projects that are not required and one for the five that want it required. I can make it required, but that would be for all projects.

This is the last piece of information. The five projects that want the Affects version to be required only want it needed on the Bug issue type.

I have thought about creating a separate field configuration for the five projects and setting the Affects version required. The other projects will be as they are and have it but not required.

I have thought about creating another custom field version of the Affect version, and I think I can make that work since it will appear separately in the field configuration. The problem with that is the 1mil+ issues that already have values in the Affect version would not transfer over to the new custom field version, but it would work moving forward.

Does that help explain it better? Thanks for being willing to brainstorm this with me!


author: Trudy Claspill
body: Thank you for that additional information.

The best solution is to create a new Field Configuration where the Affects Version field is set to Required.

Then create a new Field Configuration Scheme. In that Scheme, make the original Field Configuration the default. Then add your new Field Configuration to the Scheme associating it to only the Bug issue type.

Then apply the new Field Configuration Scheme to the five projects.

Here is an example of what the new Field Configuration Scheme might look like:

![Screenshot 2024-09-18 at 6.32.35?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/348051i75E803FB6F071417/image-size/large?v=v2&px=999 "Screenshot 2024-09-18 at 6.32.35?PM.png")


author: Alex Ortiz
body: [@donhames](/t5/user/viewprofilepage/user-id/5226196)

You'll want to create a brand new field configuration. In this new field configuration, you'll want to find the Affects version field and click on required.

From there, you'll want to create a new field configuration scheme. Then you want to click on Associate an issue type with a field configuration at the top right corner

Select Bug and then select the field configuration that we made in the first step. Click Add.

So at this point, you should have a field configuration for just bug and then the default field configuration for everything else.

Finally, go into your project(s) and go to project settings -\> issues -\> Fields -\> Actions.

Click on use a different scheme and select your new field configuration scheme. Do this for the other 4 projects.


author: donhames
body: [@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011) [@Alex Ortiz](/t5/user/viewprofilepage/user-id/4744039)

Thank you both for your quick and excellent responses. You made the solution sound so easy, and it was it! Kudos to both of you!

Now, I have a solution and have learned something new. Thank you both for sharing your knowledge. It is very appreciated!


Tags: cloud

jira-cloud