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

system field duplication

Gal Fatal

Hi,

I have some system fields duplications.

for example : target end field (it's system field which is LOCKED).

target end.jpg

I assume someone created custom field with the the same name "Target end"

Now I would like to separate them as it makes confusions everywhere across Jira.

in custom fields I see this system LOCKED field but I cannot change context or even see a clue for the addition field with the same name

target and custom.jpg

Any idea how to change the custom field name that is hiding behind the system field?

Thanks

Gal

Accepted answers

Marc -Devoteam-

Hi @Gal Fatal

A locked system field can't be changed in any way, there is no option to set a context.

It looks like the other field might be used in a Team managed project.

Check these projects.

I can confirm on creating a CF in a team managed project I don't see this filed in the custom fields section in administration

All comments

Marc -Devoteam-

Hi @Gal Fatal

A locked system field can't be changed in any way, there is no option to set a context.

It looks like the other field might be used in a Team managed project.

Check these projects.

I can confirm on creating a CF in a team managed project I don't see this filed in the custom fields section in administration

See also JSWCLOUD-25776

Gal Fatal

Hi @Marc -Devoteam-

Thank you, I did not think about the team-managed option.

Now the challenge is to find in which team-manage project this field created as I have many of them.

My opinion is Atlassian should block the option to create field with same name of system LOCKED field even if it's in team-managed project. or at least present in which project they come from.

Many thanks!

Gal

Petru Simion [Simitech Ltd.]

@Gal Fatal ,

Determining how fields are used can prove a very time consuming operation.

A field can be used in projects either as in one of the screens (create, edit, view) used in screen used in screen scheme -> issue type screen scheme -> associated to one or more projects or in workflows, where action screens(regardless if they transition to another status or not) are being used and contain a screen that contains the specific field.

If you want to optimize the system by eliminating duplicate fields this will be an extremelly time consumming operation.

If you are open to apps, you can use Fields Dashboard for Jira, an app recently released by our company.

https://marketplace.atlassian.com/apps/1235965/fields-dashboard-for-jira?hosting=cloud&tab=overview

The application will display in two tabs: Scheme and Workflows, the way each field is used in projects. Screenshot from 2024-12-14 12-22-52.png

This will give you the whole data you need in order to determine which fields are duplicated.

Data can be exported to CSV for further analysis, reporting and auditing.

You can search for all fields or filter out by projects, fields, custom vs system fields.

Regards,

Petru

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