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

Renaming JIRA custom fields

KP11

We will be renaming 10 JIRA custome fields. We have a few questions.

1. How do the fields affect existing records? Do they get updated or ignored?

2. Do Multi Select custom fields work the same way as above when renamed. What happens to current records? Updated as well? Does the Database go into heavy update mode?

Accepted answers

Harry Chan5

Are you looking at renaming the actual field or an option within a select or multi-select list?

1. Everything will get updated.

2. Everything should work the same. Everything will be updated. However, within the database everything references the ID and not the actual label/name that you give it. There won't be THAT many updates.

All comments

Harry Chan5

Are you looking at renaming the actual field or an option within a select or multi-select list?

1. Everything will get updated.

KP11

1. Both the field and also an option within multi select. Some fields wil be name only othets just multi select option.

Harry Chan5

They are all aliased. The references are in IDs. However, there will be some re-indexing going on. You *may* also need a manual reindex, but it's usually fine.

darylchuah

Any modification included renaming the Custom Fields will require to perform reindexing in order for JIRA to update the latest indexing files into the database.

Reference from this documentation: Re-Indexing after Major Configuration Changes

KP11

Thanks. There was no prompt warning from JIRA that re-index was required. Usually when we enter the Admin reindex screent it is highlighted