How can I change a shared custom field type for only one project?

[Ashley]

Not sure how to word this properly, so I'm going to try with an example. Hopefully it makes sense...

Project A, B, and C share 4 issue types. 
These 4 issue types all have unique screens/screen schemes assigned to them.
Each unique screen shares a custom field that is multi choice.

Project A wants these 4 issue types to show the multi choice custom field as a text field.

How can I change this shared custom field type for only Project A?

[John Funk]

Hi Ashley,

You can't change the type of a custom field under any circumstance. I text field is always a text field and cannot be changed. If you want the field to include a dropdown or just numbers, then you have to create a whole new field of the appropriate type. 

[Ashley]

Gotcha, ok. So, if I were to replace the multi choice with a text field on the issue type screens, would I be able to do that for only one project or would that change have to be for all projects using those issue types? 

[John Funk]

You can do that for only one project - just update the context of the custom field for that one project. 

Go to Settings > Issues > Custom fields and search for your field. 

Then click the 3 dots menu to the right of the field and select Contexts and default value. There add the project at the bottom and save it. Then only that project will have the field available to it 

[Cloudites Owner]

A Field Configuration provides the ability to change field behavior, it essentially tells Jira how to handle a particular field. For example, a Field Configuration can be used to hide a field from all input screens and views, or to make a field require a value every time it is edited.

Field Configurations are activated by placing them into Field Configuration Schemes, and then associating a scheme with one or more projects.

[Alex Koxaras -Relational-]

Hi @Ashley 

Once you have created a custom field and you have chosen its type, then that's it. You can't change its type. You need to create a new custom field of text type and place it only on project a (via field context).

[Ashley]

Gotcha - so, if I were to replace the multi choice with a text field on the issue type screens, would I be able to do that for only one project or would that change have to be for all projects using those issue types? 

[Alex Koxaras -Relational-]

Fields are associated with screens.

Screens are associated with schemes.

Schemes are associated with issue types.

With that said, you can pretty much do as you please, meaning that you have the ability to create X custom fields and choose their exact screen location. You can also restrict custom fields via field context:

E.g. You can have a multiselect field with options A, B and C and a context to be applicable only to project A.

You can then create a NEW context to be applicable to project B & C with options A, D, E and XY.

However, the field type will remain the same.