All "JIRA" strings were overwritten to "Jira" in the TAC's db which messed up JIRA Server translations

According to this ticket https://jira.atlassian.com/browse/TRANS-2466 all "JIRA" strings were overwritten to "JIra" for all the products. This has messed up translation for JIRA Server Core and JIRA Server Software.

Here is what happened:

The strings were  overwritten in Sept. However the change was only done in the DB and not in the JIRA Server code base.

In October we have imported JIRA 7.6.0 containing old "JIRA" strings. TAC recognised them as a change in english version and marked all of them for export indicating that they have changed and need translations.

A few days later  the SQL script was run again and it overwritten the JIRA strings to "Jira" again. Which created even more mess.

The current situation is that in the DB we have all the strings changed to "Jira" , JIRA Server code base still contains the old version "JIRA" and whenever we are exporting untranslated strings TAC exports ale the strings changed to "Jira".  We can't get translations  for JIRA Core  and JIRA Server 7.6.0 because TAC is showing that there are thousands of untranslated strings. The 7.6.0 release is blocked. English translations in the code base contain "JIRA" while all the translations in TAC contain string "Jira".

We would expect the translation in TAC to be reverted to "JIRA" and TAC to export only strings  actually changed in the process of developing 7.6.0