Deleted custom field still shown in JQL and apps

[Shahar Nissim]

Deleted custom field still shown in JQL and apps (even after deleting from trash) - is is very confusing as it has the same name of another field which is active.

[Nic Brough -Adaptavist-]

Sometimes, it can take a little while for the indices to catch up, especially if it's a large amount of data to empty from the trash.

If you give it a bit of time, you should find it disappears eventually (I've not seen it take longer than a couple of hours)

[Shahar Nissim]

I have the same issue for months now

[Monica Lee]

I have the same issue as well...

Having a custom text field as Build Version, the filter result is wrong (i.e. you can see tickets with empty field or other version number).

Deleting the custom field for all the issue types does not work, you can still find the custom field in the Issue View, though you can't see them when going into a ticket.

[Nic Brough -Adaptavist-]

If you've given the index enough time to catch up with the deletion of the field (when you have a large number of issues in Jira), and you are still seeing the field name in the searches, then you have not deleted the field.

I suspect you don't mean that you have deleted the field, you mean that you have cleared the data out of it for some issues.  The field still exists, even if you have no data in it for any issue.

[Shahar Nissim]

Our instance has 50K~ issues - the additional field was deleted months ago and not shown under "Custom fields" and still - when I type in JQL - both fields shown. Very frustrating and creates a lot of mess when people choose the wrong field and wonder why it's empty

[Nic Brough -Adaptavist-]

It's the same answer, you have not deleted the field from the fields, just removed it from screens.

Although there was a bug in Jira 4 that caused this behaviour for a few versions, I can't see any other way to do this in later versions.

If you are on Cloud, the likely explanation is that someone has created a field of the same name in a team-managed project.

[Shahar Nissim]

We are on cloud, and the duplicated field was indeed created in a team-managed project - but still, i deleted it from the "Custom fields" menu - is there any place else it should show?

[Nic Brough -Adaptavist-]

The custom fields list only lists custom fields that can be used by company-managed projects.

To delete a field from a team managed project, you need to go into the project and delete it from the project configuration.

[Shahar Nissim]

I tried to add a field to a team managed project and it was shown on the CUSTOM FIELD list.. I reviewed all the team managed projects in the company and the field does not exist...

[Nic Brough -Adaptavist-]

Team managed projects can now include global fields, as well as their own local fields.

I suspect you have not checked every project for your stray field.

Try a query for <custom field> is not empty.  That is likely to show you some issues that have a value for the field, and you can work out the project from their issue keys.  If you get no issues, then try <custom field is empty> - this will return issues that have the field (which will all be in one project)

[Monica Lee]

By checking from the api, I can see I have three different IDs for the custom field  with the same name "Build Version". In Issue View, while I filter by a version number, the result show a list of tickets that does not match the filter criteria. I suspect the values are added to one or two IDs when I change the value via bulk change, but when filter it shows the other ID.

While I may want to keep these fields for other projects, is there any way I can edit the value of a custom field by searching its ID?