Escalation service throws user is not configured when userKey != userName

Description

*This issue has moved*

This issue has been moved permanently to Adaptavist's Product Support JIRA instance.

All existing users of this instance should have the same username on our Product Support instance. However, you will very likely need to click on the
Can't access your account link in order to reset to a new password.

When userKey is different than the userName the escalation service throws a
"Cannot find configured user" error

Environment

JIRA v6.4.6

Assignee

Jamie Echlin

Reporter

Thanos Batagiannis [Adaptavist]

Labels

None

Internal Complexity

Unknown

Internal Value

Unknown

Fix versions

Affects versions

Priority

Major
Configure