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; } } }

Optimize Field Configs

Blum, Volker (Extern)

Hi, we have FIeld Configs with more than 900 fileds and want to clean them up. The problem with the offered "optimizer" is, that we have lots of fields that are used in a huga amount of projects and so, do nat have a defined context, but the default global one. These are considered as "unused, because the do nat have a defined context. This makes it impossible for us to use the optimizer. We do not see the opportunity to use the optimizer. Any help here?

Kind regards and cheers

Volker

Accepted answers

Arkadiusz Wroblewski

Hello @Blum_ Volker _Extern_

With 900+ fields, I recommend avoiding a purely automatic cleanup. It’s vital to separate custom field context optimization (limiting global fields to specific projects) from configuration scheme cleanup (removing fields from screens). If your fields are intentionally shared broadly, a global context is perfectly valid, and the optimizer tool isn't the right fit.

Instead, take a gradual governance approach by targeting one project family at a time. Always verify dependencies like workflows or automations, test your changes in a sandbox, and remove fields from screens first, allowing for a safe retention period before permanent deletion. If the optimizer is falsely flagging active fields, contact Atlassian Support (As Enterprise you should be entitled to extended Support); otherwise, this is best handled as a manual scoping exercise.

Best,

Arkadiusz🤠

All comments

Arkadiusz Wroblewski

Hello @Blum_ Volker _Extern_

Best,

Arkadiusz🤠

Blum, Volker (Extern)

Hi Arkadiusz,

thx for this confirmation - this is the approach that we wanted to take. This means a lot of manual work and we hope to get it done before the change to the new field scheme is implemented by ATlassian. We are afraid that this implementation includes the optimizer clean up... it is not helpful, that we do not get any information, when this will take place. So its a race...

Kind regards again

Volker

Arkadiusz Wroblewski

@Blum_ Volker _Extern_

As an Enterprise customer, you should leverage Atlassian Support to help guide this cleanup strategy. If the native optimizer lacks the dependency details you need, consider Marketplace apps like Optimizer for Jira, Field Intelligence, Field Scout, Audit 360, or Admin Toolbox for Jira.

For an Enterprise site, their true value lies in mapping exactly where fields are referencedsuch as in workflows, automations, or REST integrations before you alter them. Just ensure you vet their security and test them thoroughly in a sandbox first.

Best,

Arkadiusz🤠

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

jira-cloud-administration