How to safely delete duplicated request-type custom fields?
Asked by Nahuel Logghe:

Hi all,

I have found that I am in a similar situation as described in this article: [Unable to update "Request type" using Automation rule, getting error "Field 'customfield_xxxxx' cannot be set. It is not on the appropriate screen, or unknown. (customfield_xxxxx)" \| Jira \| Atlassian Documentation](https://confluence.atlassian.com/jirakb/unable-to-update-request-type-using-automation-rule-getting-error-field-customfield_xxxxx-cannot-be-set-it-is-not-on-the-appropriate-screen-or-unknown-customfield_xxxxx-1295390355.html)

The difference is that I can see the duplicated field is used in two projects. Is there any way to see the possible consequences of deleting it, or to find out where it is being used, before taking any action?

Thanks


Answers:
author: Brian Trepto
body: Hi [@Nahuel Logghe](/t5/user/viewprofilepage/user-id/5433828)

comments: author: Nahuel Logghe
body: Hi!


author: Marc - Devoteam
body: Hi [@Nahuel Logghe](/t5/user/viewprofilepage/user-id/5433828)

Welcome to the community.

Are these fields indeed related to a project import (this will be mentioned)?

If they are, you will first have to add all correct fields to the relevant screens.

Adjust all your request types with the new fields and bulk change all issues that used the duplicate field to retain information.

Or are you using Team managed projects, as team managed projects are like containers and the project admin can create custom fields at will and the can be named exactly the same as in another Team managed project.

Then they are different fields. Fields created in Team managed projects can't be used in other projects.

Then you would need to switch to a company managed projects.

comments: author: Nahuel Logghe
body: Thank you for the welcome and the response; I was expecting it to take more time to receive an answer :D. Yes, they are "Request type created by JIM during import process." I'll see if I can solve it with this, and if not, you'll see me back here with more questions.

Thanks again


author: andylee
body: Hi,

I have a similar issue but not sure where to ask for help. We are using Team Managed Project. We accidentally created several duplicate fields in Request Types. I've delete it from both the form as well as the right panel but when using advance search, these fields are still showing up. For example, we accidentally created a second field called "First Name." I've deleted it in from Request Types page. I then performed an advance search and it still shows 2 First Name fields. Not sure if I'm doing something wrong or if there is a different solution.

Thank you,

Andy


author: Marc - Devoteam
body: Hi [@andylee](/t5/user/viewprofilepage/user-id/4335662)

Or are you using Team managed projects, as team managed projects are like containers and the project admin can create custom fields at will and the can be named exactly the same as in another Team managed project.

Then they are different fields. Fields created in Team managed projects can't be used in other projects.

Removing it from the Request Type page doesn't remove the field from Jira.

You will still need to remove the field from the field section on the project.


author: andylee
body: Hello Marc,

Thank you for your reply. We are using Team Manage Projects. I don't see a Fields section. The only Fields section that I see is a side panel to the right of the Request Types window. If it is here then I've deleted it already.

![Screenshot 2024-02-23 at 9.29.28?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/308425i7CABB8D5683B1171/image-size/large?v=v2&px=999 "Screenshot 2024-02-23 at 9.29.28?AM.png")


author: Marc - Devoteam
body: Hi [@andylee](/t5/user/viewprofilepage/user-id/4335662)

Then it should be gone, or another team managed project in your instance uses a field with the same name.

This is due to using team managed projects. They are like containers, fields made in team managed projects only exist in their project and not in others.

If you want to make use of a single field in all projects and not have duplicate ones. Your only option is company managed projects, as they are able to share custom fields in the system


author: andylee
body: Thanks [@Marc - Devoteam](/t5/user/viewprofilepage/user-id/3796976) .

Because other teams have the same name, I will need to change the naming standard for all teams so that they each will have their own unique field names.


Tags: cloud

custom-field

jira-service-management

jira-service-management-cloud

request-type