Summary

After migration from Jira server to Jira cloud, whenever customers (Jira Service Desk) are reverted back to users, the user key is recorded as a hash in the format:

• qm:hash1:hash2

This is a large string that is recorded under the user tables of Jira and there might be tables that don't allow the number of characters.

Problem

A scenario which this is happening is when adding a single user with this characteristic to a notification scheme.

The notification scheme table doesn't allow this action because the user key exceeds the number of allowed characters.

Workaround

Set up the notification scheme by groups or roles instead of single-user.