We are also getting user specific error while cloning. How to resolve them?

[m]

We are also getting user specific error while cloning. like... - Assignee=user 'XXXX' does not exist. - Reporter=The reporter specified is not a use. - Exception: An Exception occurred while cloning the issues corresponding to the specified user.

Screen Shots

1

image2015-1-7 16:38:46.png

2

image2015-1-7 16:39:46.png

3

image2015-1-7 16:40:26.png

[Lars Broden]

Hi,

This might mean that the Reporter or the Assignee of the source Issue was Removed or disabled from The jira-users group. Can you check if the Reporter or the Assignee of that issue exists in JIRA or if it is disabled?

[Richard Caton]

We are getting the same problem.  Our users definitely exist and have not been disabled or removed.  However the name shown in the error message doesn't correspond correctly to our usernames.  For instance, when we get the following error:

Errors: {reporter=The reporter specified is not a user., assignee=User 'matthew' does not exist.} Error Messages: []

The issues are assigned to me, however my display name is "Matthew Faupel" and my login id is matthewf, neither of which corresponds to "matthew".  Note that the issues display correctly within JIRA and "matthew" has never been a valid login name for the system.  I'm wondering whether it's somehow going wrong because of the space in the display name?