Strange names in Custom fields.

Question

My team is migrating its HelpDesk to Jira, so this is a fresh new installation not implemented yet. Certain fields have strange and uncomfortable long names. In the following screenshot you can see the 4 fields in question and how one of them is displayed on the ticket.

Since it's a new installation I tried to reinstall everything cleanly without Backup. Nothing changed. Also as one of the fields appears in arabic (yeah weird) I thought it could be a language conflict because the first installation was in spanish. So I tried installing everything in english. (Windows still in spanish tho)

Since the fields are LOCKED, I can not rename them. According to this article it is possible to unlock them from the DB but can not access it. How to unlock a Locked Jira Software Field

Specifically, my team requires using the fields sd.customer.organisations.field.name and sd.origin.customfield.default.name. I would need to know how to avoid the problem or how to access the DB to rename them.

Thank you.

Alejandro Fredes · Answer

There is another post where someone said the following:

There is a bug specific for Service Desk and another one that affects some fields on Software but also mention about Service Desk:
- https://jira.atlassian.com/browse/JSDSERVER-6396
- https://jira.atlassian.com/browse/JRASERVER-69388
Please, click on "This affects my team" and watch to receive updates about the bugs

Nic Brough -Adaptavist- · Answer

This error is an odd one, the values you see on screen are really references to language files that should map references like "red.dwarf.penguin.fry" to the text "Mr Flibble says it is time to die". But Jira should be reading the Spanish language file.

The reason for that is that "red.dwarf.penguin.fry" can be embedded in code, but Jira knows that means "look up the translation into human for the current person".

The problem you have here is that Jira can't find and/or read the file that translates the keys into human language.

Your instinct about the Spanish install is probably right in most ways - there's something wrong with Jira's access to the translations from Aussie/SF-geek to any-other-language.

I would start with checking that the account running Jira is the owner (with full rights) of the files that Jira is installed with, and its home directory.  If this is ok, then the next place to look is the application logs for errors.

Nic Brough -Adaptavist- · Answer

Dammit, can only vote once!

As soon as you mention looking at the database, I can tell you that you are looking at a bad thing to do.  It looks complex (because it is), and it looks scary, and rightly so, because amending it is almost certainly going to break it.  A lot.  Do not.