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

Did Atlassian change the name of custom fields for epics during some versions

Florian Engertsberger

Hi,

I have a (very old) JIRA productive system which is on 7.5.2.
Then I have a new created JIRA test system which is on 7.10.2.

When I take a look to the custom fields of both systems epic custom field on the 7.5.2 are named "Epic Name", "Epic Status" etc. and they are locked.
On the 7.10.2. these fields are named "Epic-Name", "Epic-Status", etc. (so with a "-" in the middle) and they are also locked.

That causes some troubles when trying to use addons like the Botronsoft Configuration Manager.

Does anybody know if atlassian changed the names of the epic custom fields or why the names differ between that different JIRA versions?

Thanks for replies,
Flo

Accepted answers

Florian Engertsberger

So @Christos Moysiadis ´s hint regarding the German language was the breakthrough. Installing JIRA with system language German will cause that the epic custom fields are hyphened ("Epic-Name"). That´s what happened to my testsystem and is has nothing to do with different JIRA versions (like @Nic Brough -Adaptavist- already suspected).

I installed JIRA on a VM last night several times with different versions and different system languages and everytime I uses German as system language I got hyphened epic custom fields.

So thanks a lot for your help guys.

All comments

Nic Brough -Adaptavist-

No, they did not change the names of any fields.

I suspect one of your admins has looked up "how do I unlock locked fields in Jira", used it and renamed them. There's a reason they are locked - to prevent poorly understood changes like this one having such an impact.

Christos Moysiadis

@Nic Brough -Adaptavist- i had the same issue during an integration. I noticed the same changes. The Jira Software version was 7.3.2 and the other 7.13. Strange is that in both Jira's, administatrator is/was the same! So i dont i think he changed the one and left the other in order.

Are you 100% sure that Atlassian didn't changed anything ??? I doubt a lil bit , always with no offence here .

Regards

Florian Engertsberger

@Nic Brough -Adaptavist-I also talked to our administrator and no manual changes to theses fields have been made.

Christos Moysiadis

Hello together again...

I don't know if it plays any role that my old Jira software (7.3) was in German Language!

Florian Engertsberger

I installed JIRA on a VM last night several times with different versions and different system languages and everytime I uses German as system language I got hyphened epic custom fields.

So thanks a lot for your help guys.

Christos Moysiadis

Always happy to help @Florian Engertsberger

Regards

Nic Brough -Adaptavist-

Nice! That was the next thing I was going to try when I had time to do so.

Whilst I understand that the hyphenation by default is good for German speakers sometimes, it's extremely bad that it breaks things this way, and very annoying that it works differently when swapping to your own language when it's not the default. That's a howling bug, in my opinion!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

custom-field

jira-software

jira-software-server

epic