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

Field administration -> Field names now show with translated name instead of technical name

Becker_ Rene

Hey all.

I just noticed, that in "Jira Admin Settings" -> "Fields" now show their translated name instead of the technical name.

Example:

For the backend, I have a name scheme for fields. It goes something like

"Alternative Internal Item Number (11816) - Plain Text"

Now it shows: "Alternative Interne Nummer" (German translation)

When I update "Name" it reverts back to the translated name and ignores, that I changed the name.

---

This is done to easily identify the field name when I create new forms and when I search for them later on and have all data I need in the name.

I then use translations to make fields show in the respective name, when users or I view the actual work item via the regular view.

---

Question: Is it just me? Anyone know how to revert this?

---

thx, regards

Rene

Accepted answers

Isabelle Ruivo dos Santos

Hi, @Becker_ Rene!

What's going on

It's not just you — this is a recent change in Jira Cloud. The admin Fields screen now displays the translated field name based on your profile/browser language instead of the original technical name. The original name is still stored in the backend, so this is a UI display issue rather than a data problem.

Workarounds

Temporarily switch your profile language to English — go to Profile → Account Settings → Language → English, then revisit the Fields page. It should display the original backend name. Switch back when you're done.
Verify via REST API — the GET /rest/api/3/field endpoint always returns the original field name regardless of translations. Useful for confirming your naming convention is intact.

Hope this helps!

All comments

Marc -Devoteam-

HI @Becker_ Rene

Is there a translation on the field set?

What is you language in your account settings set to? or your browser language or regional settings.

Can you check using another browser or incognito window?

Becker_ Rene

Thank you for your response.

Yes, a translation is set.

Here are a few more details:

A few days ago:

- Create a field

- name it "My Field for Stuff (12345) - Text"

- Add Translations ("A German Name 1", "An English Name 1")

-> In Admin Area name shows as "My Field for Stuff (12345) - Text"

-> In Work Items view masks it shows, depending on the Browser / User Language either "A German Name 1" or "An English Name 1"

Now:

- Create a field

- name it "My Field for Stuff (67891) - Text"

- Add Translations ("A German Name 2", "An English Name 2")

-> In Admin Area name shows as "A German Name 2" (resp. "An English Name 2")

-> In Work Items view masks it shows, "A German Name 2" or "An English Name 2"

--> In the Admin Area it should show "My Field for Stuff (67891) - Text"

EDIT: Sorry, I messed up the labels when I posted.

Conclusions:

Admin Section -> Fields -> now shows translation instead of the original name

Additionaly:

When I try to change the original field name, the change does not stick.

---

I recreated the problem by creating a new field

(Picture 7 -> should display "[CF] Test Field name display by Atlassian (1234)" not "[CF] Test Field Name display by Atlassian (xxx) - UK"

Isabelle Ruivo dos Santos

Hi, @Becker_ Rene!

What's going on

Workarounds

Temporarily switch your profile language to English — go to Profile → Account Settings → Language → English, then revisit the Fields page. It should display the original backend name. Switch back when you're done.
Verify via REST API — the GET /rest/api/3/field endpoint always returns the original field name regardless of translations. Useful for confirming your naming convention is intact.

Hope this helps!

Becker_ Rene

Marc -Devoteam-

HI @Becker_ Rene

I tried thia, but this doesn't chnage on my end.

My account setting are UK and browser is also UK and laptop is English and Location NL.

All Atlassian details are shown in English UK, even on adding dutch trasnlations.

So it seems to be a browser, laptop or Atlassian instance related issue, you could raise an issue with Atlassian Support

Becker_ Rene

Thank you for your response.

I worked ... in parts :-D

Some fields are now shown by their correct name, some still show translated.

With every page reload more and more revert to their translated name, instead of the backend name.

---

As you said, existing fields are visible via API.

The new one somehow not.

But I can retrieve it on /rest/api/3/field/customfield_13645/context

{
"maxResults": 50,
"startAt": 0,
"total": 1,
"isLast": true,
"values": [
{
"id": "20403",
"name": "Default Configuration Scheme for [CF] Test Field name display by Atlassian (xxx)",
"description": "Default configuration scheme generated by Jira",
"isGlobalContext": true,
"isAnyIssueType": true
}
]
}

I'll just assume it's there and I somehow am not seeing it.

---

Becker_ Rene

I worked through the topic with Atlassian's support.

The change (displaying the translated name instead of the backend name of a custom field) was done intentional by Atlassian.

The reason that was stated, is that there were too many complaints from Administrators, that got confused / annoyed that the backend name differs from the translated one (... I don't get it).

The bug where the name did not change when updated was fixed.

While I absolutely cannot understand the change (for me it's the direct opposite of the overview's purpose), there was a bit of a compromise:

- The Development Team was made aware and maybe we can expect at least an on/off switch (not confirmed)

- The backend-name and the translated name (as well as ID and description) are searchable.

In the end I will switch over to API and have it generate CSV or something like that.

Thanks for your input :-)

---

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