nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is it possible to remove the custom fields from the field configuration?

Natalia Trofimov

We are migrating projects from jira server to the diff jira cloud instances. The field configuration have unused custom fields inherited from other projects and we don't want those unused custom fields to be migrated if they are not used by the projects. Is it possible to remove unused custom fields from the field configuration so they are not migrated to cloud. My understanding If we hide the custom fields from the field configuration in jira server, the values of the custom fields are not migrated but the custom fields are still migrated. Is it a way to clean it up?

Thank you,

Natalia

Accepted answers

Nic Brough -Adaptavist-

No, the field configurations don't actually contain any fields, they're an array of settings for every field that exists in your system, irrespective of usage.

You can't remove something that isn't there in the first place!

The only place custom fields actually exist is in, well, the list of custom fields. Check in there for the field "context" though - that's what determines whether a field is part of a project or not, and if a field has no context for the project you are moving over, it won't be taken across.

All comments

Nic Brough -Adaptavist-

No, the field configurations don't actually contain any fields, they're an array of settings for every field that exists in your system, irrespective of usage.

You can't remove something that isn't there in the first place!

Natalia Trofimov

Hi Nic,

Great answer! Thank you I just learned something new!

I have one more question then.

We are migrating the projects from our Jira server to the different cloud sites for diff departments so they would have their own sites.

What is the best practice not to bring the custom fields that are not used in their projects to their sites? bc the filed configurations bring all custom fields “arrays” to their sites. Those custom fields don’t have contexts but they are still listed. Even if we hide the custom fields in the field configuration on the server bf migration and the values of the custom fields are not migrated, the custom fields are still taking across and they are listed on their sites. How to clean it up? Should we delete unused custom fields on the cloud sites after migration?

Please advise,

Thank you,

Natalia

Nic Brough -Adaptavist-

Personally, I tend to use tools that won't bring them across if I don't want them, but I think you're using JCMA, which doesn't give you the option. Deleting after migration is probably the most simple thing you can do here.

Natalia Trofimov

Hi Nic

yes, we are using JCMA.

Thank you very much! Greatly appreciated!

Best,

Natalia

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-cloud

jira-software-server