Custom field context change from global to team

[Sanbileg Arkhad]

Hi,

in my company there are many custom fields that are set to global context. My task is to clean it up and make only very few key custom fields as global.

I tried to change the context of the custom fields from global to the corresponding team projects in the context editing screen, but the global option still persists.

My solution was to create a new context for the custom field with all the settings I need and just delete the old one.

I researched what the consequences would since these custom fields contain important information and my question would be:

What are the consequences when I create a new project based context for a custom field?

What are the consequences when I delete the old context?

Thank you!

[Shawn Doyle - ReleaseTEAM]

Hi @Sanbileg Arkhad 

As long as you set the field context to the projects and issue types that are currently using them, you will be fine.

[Marc - Devoteam]

HI @Sanbileg Arkhad 

Welcome to the community.

In your example screenshot the custom field is now only usable in the selected project, but for all the work item types in that project.

If you delete the old context, all work items that had a value in this field, will have this value deleted from the system.

If you create a new project and wnat to make use of the custom field in the project, you will have to create a new context on the custom field or adjust the existing context.

You can select multiple projects and or work item types, by holding the Control or Shift key