Sorry for the notification, accidentally triggered the shortcut keys

This issue seems not just affecting the Request Name / Display Name, but most of the Service Desk element. This is what have been reported by a user:

1. Queue name: Service desk -> Queues -> Add new queue -> add queue name «Новая очередь» -> Create -> result is «????? ???????».
2. Report name: Service desk -> Reports -> New report -> add report name «Новый отчет» -> Create -> result is «????? ?????».
3. Label name at report series: Service desk -> Reports -> Edit -> Add a series -> add label name «Метка» -> Add & Save -> result is «?????».
4. SLA metric name: Service desk -> SLA -> new metric -> add metric name «Новая метрика» -> assign any START and STOP conditions -> save & update -> resuli is «????? ???????».
5. Calendar name: Service desk -> SLA -> Calendar -> new calendar -> add calendar name «Календарь» -> save -> result is «?????????».
6. Holyday name: Service desk -> SLA -> Calendar -> edit calendar -> add holyday name «Праздник» -> save & update -> result is «????????».
7. Request name and groups: Service desk -> Settings -> Request types -> add request name « Название запроса» and group name « Группа» -> add -> result «???????? ???» at request name and «??» at group name.
8. Workflow status name to show customer: Service desk -> Settings -> Request types -> edit fields -> Workflow Statuses -> add status name to show customer «Статус» -> Save -> result is «??????».
9. Customer portal name: Service desk -> Settings -> Portal settings -> change customer portal name to « Центр поддержки» -> save -> refresh screen or navigate to customer portal -> result -> « ????? ?????????».
10. Confluence space name: Service desk -> Settings -> Confluence KB -> Link to a knowledge base -> Select application Confluence -> Select space named «Документы» -> Link -> result space name «?????????».
11. Label name at article restrict: Service desk -> Settings -> Confluence KB -> add a Confluence label «Метка» at Restrict to articles with labels -> Update & refresh screen -> result is «?????».
12. Automation rule name and description: Service desk -> Settings -> Automation -> New rule -> for example Custom rule -> add rule name «Правило» and rule description «Описание» -> add any condition and action at WHEN IF THEN -> Save -> open created rule -> result «???» at rule name and «????» at rule description.

Cheers,
Julian.

This has been fixed in the underlying ActiveObjects library, and will be available with the next major release for new instances of JIRA.

Existing tables will not be updated, due to its complexity and risk.

Therefore best suggestion would be to export to zip, create a new JIRA instance, then import.

cnguyen Is there a related issue we can follow to track progress? I hope this is something that is going to be fixed soon.

Thanks a lot Alext1. From my understanding this a ActiveObjects framework bug right, it should be handled transparently when creating tables on SQL Server to use nvarchar column type, no? Is this raised as an issue somewhere?

aggelosp, we've been advised by Atlassian support to change collation of the database to resolve that. But since we are on Microsoft SQL database, the issue was not with collation, but with field type. All plugins use database tables that have varchar and text field types. But for unicode nvarchar and ntext are necessary. So, we changed the database definition for the relevant fields, and it works now!

Look for tables AO_54307E_xxxxxx.

Same problem here, I believe it's Windows OS related. On MacOS we have no problems with Greek characters on request names, queues etc.

Alex, any news from SDS-4089 you can share before we submit another ticket as well?

Hi,

I have created a ticket: SDS-4089.

Alex

Hi Alex Timofeyev,
Could you create a support ticket at https://support.atlassian.com?
That way we can provide you with support specific to your circumstances and with higher security.
The credentials should be the same as for this site (https://jira.atlassian.com).
Thanks!
JIRA Service Desk Product Team