Changes in language-pack-en-US version 8.15.0.20210809004541? - Problems with terminology changes

Question

Does anyone know about the changes that have been introduced to the language-pack version:

Index of maven-internal/com/atlassian/translations/jira-software-language-pack-en_US/8.15.0.20210809004541

Compared to the version:

Index of maven-internal/com/atlassian/translations/jira-software-language-pack-en_US/8.14.0.v20200826125100

It's quite som differences between the versions in the file named BoardAction_en_US.properties in this package.

I've earlier made some changes to this file to adopt to the SAFe terminology. Now that I upgraded our Jira Software Server instance to 8.20.4 I realized that this file has changed a lot. I'm not sure I can run Jira Software 8.20.4 with my "old" language-pack or if I should adjust the new language-pack?

Since there are so many changes I'm not sure I can. It also seems that the term Epic no longer is defined in the BoardAction-file. Maybe this has to do with the changes that Atlassian announced concerning "Flexible Terminology"?

We're still running on Jira Software Server licens and I can't see the Terminology-page in Jira Admin pages that Atlassian refers to in this new Feature for flexible terminology.

Do you need Jira Software Data Center licens for that?

Regards

Lotta Löfwall

Lotta Löfwall · Answer

Ok, thank you for your answer. I think I have to stay with the old language-file until we upgrade to DC. But now I at least know how it works :)

Nic Brough -Adaptavist- · Answer

Yes, you are absolutely right about the changes - a lot of them are there to support the ability to fully rename Epic, but a lot of them are there to support changes and improvements across the system.

My recommendation is definitely to adapt the new language file, not reuse your old one.

It won't actually break anything if you use the old one, but you will find words going wrong in the UI when Atlassian has added a phrase to the new version, or renamed a key.  (You'll get the key appearing on the screen instead of the content).

Yes, flexible-terminology is only enabled for DC installs.  Server probably won't get it, as it's going away in a couple of years.