System Event Names are not translated to the user profile's language in the notification scheme page
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
When checking on the notification scheme the name of System Events are not displayed in the correct language as set per Default Language for Jira, and/or they do not get translated based on the user profile setting.
Environment
Jira 7.x, Jira 8.x
Cause
The names of the events are stored in the jiraeventtype table within the Jira database. Previous versions of Jira have stored the translated name and description of the event. In Jira 7.x and 8.x the names should be stored in English, and would be translated based on the setting in Jira.
To check this run
1
select * from jiraeventtype;Solution
Always back up your data before making any database modifications. If possible, test any alter, insert, update, or delete SQL commands on a staging server first.
Stop JIRA
⚠️ Backup your database
Run the following queries in the database:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
update jiraeventtype set name = 'Issue Created', description = 'This is the ''issue created'' event.' where id = 1;
update jiraeventtype set name = 'Issue Updated', description = 'This is the ''issue updated'' event.' where id = 2;
update jiraeventtype set name = 'Issue Assigned', description = 'This is the ''issue assigned'' event.' where id = 3;
update jiraeventtype set name = 'Issue Resolved', description = 'This is the ''issue resolved'' event.' where id = 4;
update jiraeventtype set name = 'Issue Closed', description = 'This is the ''issue closed'' event.' where id = 5;
update jiraeventtype set name = 'Issue Commented', description = 'This is the ''issue commented'' event.' where id = 6;
update jiraeventtype set name = 'Issue Reopened', description = 'This is the ''issue reopened'' event.' where id = 7;
update jiraeventtype set name = 'Issue Deleted', description = 'This is the ''issue deleted'' event.' where id = 8;
update jiraeventtype set name = 'Issue Moved', description = 'This is the ''issue moved'' event.' where id = 9;
update jiraeventtype set name = 'Work Logged On Issue', description = 'This is the ''work logged on issue'' event.' where id = 10;
update jiraeventtype set name = 'Work Started On Issue', description = 'This is the ''work started on issue'' event.' where id = 11;
update jiraeventtype set name = 'Work Stopped On Issue', description = 'This is the ''work stopped on issue'' event.' where id = 12;
update jiraeventtype set name = 'Generic Event', description = 'This is the ''generic event'' event.' where id = 13;
update jiraeventtype set name = 'Issue Comment Edited', description = 'This is the ''issue comment edited'' event.' where id = 14;
update jiraeventtype set name = 'Issue Worklog Updated', description = 'This is the ''issue worklog updated'' event.' where id = 15;
update jiraeventtype set name = 'Issue Worklog Deleted', description = 'This is the ''issue worklog deleted'' event.' where id = 16;
update jiraeventtype set name = 'Issue Comment Deleted', description = 'This is the ''issue comment deleted'' event.' where id = 17;
update jiraeventtype set name = 'Issue Archived', description = 'This is the ''issue archived'' event' where id = 18;
update jiraeventtype set name = 'Issue Restored', description = 'This is the ''issue restored'' event' where id = 19;⚠️ This queries have been tested with Postgres and might need to be adjusted for other databases. ⚠️
Re-start JIRA
Was this helpful?