Jira server throws there is no ID mapped for the user key error

[Sandro Steiner]

sometimes our jira environment is slow, so i analysed the error log.

we have 110 times the error " Jira server throws there is no ID mapped for the user key error" and i followed the instruction on the knowledgebase: https://confluence.atlassian.com/jirakb/jira-server-throws-there-is-no-id-mapped-for-the-user-key-error-770606447.html?utm_medium=logScan&utm_source=STP

our error:

2020-10-20 12:06:28,820+0200 http-nio-80-exec-8 ERROR anonymous 726x14993x1 10lksn4 172.19.20.74 /CSAction!save.jspa [c.a.event.internal.AsynchronousAbleEventDispatcher] There was an exception thrown trying to dispatch event [com.atlassian.jira.event.issue.IssueEvent@315c9fdc[issue=HEL-722,comment=com.atlassian.jira.issue.comments.CommentImpl@6df12b10,worklog=<null>,changelog=<null>,eventTypeId=6,sendMail=true,params={eventsource=action, baseurl=http://xxxxx},subtasksUpdated=false,spanningOperation=Optional.empty]] from the invoker [SingleParameterMethodListenerInvoker{method=public void com.atlassian.jira.bc.issue.watcher.AutoWatchService.onIssueEvent(com.atlassian.jira.event.issue.IssueEvent), listener=com.atlassian.jira.bc.issue.watcher.AutoWatchService@52c10698}]
java.lang.RuntimeException: There is no ID mapped for the user key 'admin'. Listener: com.atlassian.jira.bc.issue.watcher.AutoWatchService event: com.atlassian.jira.event.issue.IssueEvent
at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:57)
at com.atlassian.event.internal.AsynchronousAbleEventDispatcher.lambda$null$0(AsynchronousAbleEventDispatcher.java:37)
at com.atlassian.event.internal.AsynchronousAbleEventDispatcher.dispatch(AsynchronousAbleEventDispatcher.java:85)
at com.atlassian.event.internal.LockFreeEventPublisher$Publisher.dispatch(LockFreeEventPublisher.java:220)
at com.atlassian.event.internal.LockFreeEventPublisher.publish(LockFreeEventPublisher.java:96)
at com.atlassian.jira.event.issue.DefaultIssueEventManager.publishEventIfNotificationsAreEnabled(DefaultIssueEventManager.java:180)
at com.atlassian.jira.event.issue.DefaultIssueEventManager.publishEvent(DefaultIssueEventManager.java:162)
at com.atlassian.jira.event.issue.DefaultIssueEventManager.publishAsRedundant(DefaultIssueEventManager.java:204)
at com.atlassian.jira.event.issue.DefaultIssueEventManager.dispatchRedundantEvent(DefaultIssueEventManager.java:91)
at com.atlassian.jira.issue.comments.CommentEventPublisherImpl.publishCommentCreatedEvent(CommentEventPublisherImpl.java:57)
at com.atlassian.jira.issue.comments.DefaultCommentManager.create(DefaultCommentManager.java:288)
at com.atlassian.jira.issue.comments.DefaultCommentManager.create(DefaultCommentManager.java:239)
at com.atlassian.jira.issue.comments.DefaultCommentManager.create(DefaultCommentManager.java:229)
at com.atlassian.jira.issue.comments.DefaultCommentManager.create(DefaultCommentManager.java:213)
at com.atlassian.jira.issue.comments.DefaultCommentManager.create(DefaultCommentManager.java:202)
at com.atlassian.jira.issue.comments.DefaultCommentManager.create(DefaultCommentManager.java:191)
at com.atlassian.jira.issue.comments.DefaultCommentManager.create(DefaultCommentManager.java:196)
at ru.teamlead.jira.plugins.cs.actions.CSAction.doExecute(CSAction.java:525)
at ru.teamlead.jira.plugins.cs.actions.CSAction.doSave(CSAction.java:273)
... 3 filtered
at java.lang.reflect.Method.invoke(Method.java:498)
at webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtils.java:70)
at webwork.util.InjectionUtils.invoke(InjectionUtils.java:56)
... 2 filtered
at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:63)
... 7 filtered
at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
... 52 filtered
at com.atlassian.jira.plugin.mobile.web.filter.MobileAppRequestFilter.doFilter(MobileAppRequestFilter.java:59)
... 4 filtered
at com.atlassian.jira.plugin.mobile.login.MobileLoginSuccessFilter.doFilter(MobileLoginSuccessFilter.java:54)
... 3 filtered
at com.atlassian.diagnostics.internal.platform.monitor.http.HttpRequestMonitoringFilter.doFilter(HttpRequestMonitoringFilter.java:55)
... 8 filtered
at com.atlassian.web.servlet.plugin.request.RedirectInterceptingFilter.doFilter(RedirectInterceptingFilter.java:21)
... 57 filtered
at com.atlassian.jira.security.JiraSecurityFilter.lambda$doFilter$0(JiraSecurityFilter.java:66)
... 1 filtered
at com.atlassian.jira.security.JiraSecurityFilter.doFilter(JiraSecurityFilter.java:64)
... 39 filtered
at com.atlassian.jira.servermetrics.CorrelationIdPopulatorFilter.doFilter(CorrelationIdPopulatorFilter.java:30)
... 10 filtered
at com.atlassian.web.servlet.plugin.request.RedirectInterceptingFilter.doFilter(RedirectInterceptingFilter.java:21)
... 4 filtered
at com.atlassian.web.servlet.plugin.LocationCleanerFilter.doFilter(LocationCleanerFilter.java:36)
... 29 filtered
at com.atlassian.jira.servermetrics.MetricsCollectorFilter.doFilter(MetricsCollectorFilter.java:25)
... 25 filtered
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalStateException: There is no ID mapped for the user key 'admin'
at com.atlassian.jira.user.DefaultUserPropertyManager.getPropertySetForUserKey(DefaultUserPropertyManager.java:32)
at com.atlassian.jira.user.DefaultUserPropertyManager.getPropertySet(DefaultUserPropertyManager.java:25)
at com.atlassian.jira.user.preferences.DefaultUserPreferencesManager.getExtendedPreferences(DefaultUserPreferencesManager.java:22)
at com.atlassian.jira.bc.issue.watcher.AutoWatchService.isAutoWatchEnabledForUser(AutoWatchService.java:88)
at com.atlassian.jira.bc.issue.watcher.AutoWatchService.shouldAutoWatchEvent(AutoWatchService.java:66)
... 2 filtered
at java.lang.reflect.Method.invoke(Method.java:498)
at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:42)
... 281 more

sql command is

SELECT * from userassociation WHERE association_type = 'WatchIssue'
AND source_name = 'admin'

and the result was NULL

-> If the query above returns any results, please proceed to the next steps. Otherwise, contact Atlassian Support.

[Randall Robertson · Accepted solution]

It sounds like you are confusing groups with project roles. The User Manager page shows you what groups the user account is part of. Those groups may be added to project roles to give everyone in that group a project role, but the groups themselves are not project roles. The link you click from the user manager page to see the user's roles only lets you view the roles. As @rambanam mentioned, use the project role admin feature in each project (in our JIRA 5.1 instance, it is the People tab in the project admin page) to grant the user the necessary project roles.

[Vanessa]

Apologies, I have been on leave. I have now sorted the issue: User Management>select the username you are after>select view project roles>select 'roles' from the left hand nav>select 'view usage'>select 'view'>select edit and then add your user.

However, I have done this on several occasions, but it has now worked!

Thankyou for all your suggestions and help.

[Udo Brand]

Have you checked if the user or the project role have 'Browse Project' permission?

[Vanessa]

I have just logged on as the user I am having issues with. There are 2 issues assigned to him and I have selected 'My Open Issues' and I have two new messages:

• Field 'assignee' does not exist or you do not have permission to view it.
• Field 'resolution' does not exist or you do not have permission to view it.

[Vanessa]

Thanks Nic, I have checked the other users and there are no differences apart from there is no option to select Project Roles through User Management for this user and he has no drop downs when you log into his account. So frustrating and I bet is is something really simple!

[Nic Brough -Adaptavist-]

Sorry, I was asking specifically about groups and roles, not what the admins can do with the user.

"Field X does not exist or you do not have permission to view it" usually means the user has no rights to see the issue! What happens when you log in as them and visit a specific issue (that you can see with your account)?

[Vanessa]

I have granted the project roles to the user and each area I can see he has those roles. I updated them as advised by rambanam and this did not make any difference when the user logged in. Nic, I have deleted the user and set him up twice, I have checked his login details and he is logging into the correct account. I do not see a Permissions Helper tool in the More Actions dropdown, I will have another look and update you.

[Nic Brough -Adaptavist-]

Ok, it was worth ruling out.

Next thing to do - find another user who can log in and see stuff ok, then compare their groups and roles. Are there ANY differences in either groups or roles?

(Also, long shot - can they try logging in from your machine where you know it works for you?)

[Randall Robertson]

Do you see the Permissions Helper tool in the More Actions dropdown when viewing an issue in this project? If so, you can use that to find out what permissions jira thinks the user has in the Project. It will tell you what group or role he needs to be in if this is simply a permissions problem.

[Vanessa]

Project role from the project administration page did let me add the relevant project roles to the user. However, when the user logs in he only has 'Dashboards' along the top tool bar. It also states there are no issues assigned to him even though two have been assigned to him and display that they are assigned to him.

[Nic Brough -Adaptavist-]

Can you check the exact login details for the user? I've run into similar problems where we've got two similar accounts - nothing looks wrong with account 1, but it turns out the user is logging into account 2, which is subtly different and in the wrong roles.

[RambanamP]

you can add to project role from project administration page, got to the project administration page and select project role, there you can add him to which ever you want to add