Cannot create issue in JIRA
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
When click on the create issue button, after filling in the details and click on 'Create' , nothing happens
When safe mode is turned on, performing the test again will lead to the following exception is shown on the screen (page 500)
The following appears in the atlassian-jira.log
1
2
3
4
5
6
7
8
9
10
11
12
13
java.lang.NoSuchMethodError: com.atlassian.jira.event.issue.IssueEvent.getUser()Lcom/atlassian/crowd/embedded/api/User;
at org.openmrs.jira.listeners.AutowatchJiraListener.issueCreated(AutowatchJiraListener.java:100) [?:?]
at com.atlassian.jira.event.issue.AbstractIssueEventListener.workflowEvent(AbstractIssueEventListener.java:124) [jira-api-7.0.5.jar:?]
at com.atlassian.jira.event.issue.IssueEventListenerHandler$IssueEventInvoker.invoke(IssueEventListenerHandler.java:43) [IssueEventListenerHandler$IssueEventInvoker.class:?]
at com.atlassian.event.internal.AsynchronousAbleEventDispatcher$1$1.run(AsynchronousAbleEventDispatcher.java:48) [atlassian-event-2.3.5.jar:?]
at com.google.common.util.concurrent.MoreExecutors$DirectExecutorService.execute(MoreExecutors.java:299) [guava-18.0.jar:?]
at com.atlassian.event.internal.AsynchronousAbleEventDispatcher.dispatch(AsynchronousAbleEventDispatcher.java:107) [atlassian-event-2.3.5.jar:?]
at com.atlassian.event.internal.EventPublisherImpl.invokeListeners(EventPublisherImpl.java:160) [atlassian-event-2.3.5.jar:?]
at com.atlassian.event.internal.EventPublisherImpl.publish(EventPublisherImpl.java:79) [atlassian-event-2.3.5.jar:?]
at com.atlassian.jira.event.issue.DefaultIssueEventManager.publishEvent(DefaultIssueEventManager.java:120) [DefaultIssueEventManager.class:?]
at com.atlassian.jira.event.issue.DefaultIssueEventManager.publishAsRedundant(DefaultIssueEventManager.java:132) [DefaultIssueEventManager.class:?]
at com.atlassian.jira.event.issue.DefaultIssueEventManager.dispatchRedundantEvent(DefaultIssueEventManager.java:83) [DefaultIssueEventManager.class:?]
at com.atlassian.jira.workflow.function.event.FireIssueEventFunction.execute(FireIssueEventFunction.java:58) [FireIssueEventFunction.class:?]Cause
This is caused by JIRA Autowatch plugin. It is a chain reaction due to a crowd configuration is having an issue of finding particular
Workaround
Delete the Autowatch Plugin from the
$JIRA_HOME/plugins/installed-plugins
Resolution
Ensure that your crowd are configured properly and no exception exist in your atlassian-jira.log
Was this helpful?