"No Activity was found" shown in every activity tab in Jira issues

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

Summary

On loading the activity tab in the Jira ticket, it does not shows the contents as expected instated an error No Activity was found is noticed in every Issue when going to the activity tab. Something similar is observed with activity stream gadgets.

Environment

  • v8.x and onwards

Diagnosis

On reviewing the atlassian-jira.log, following java.lang.NullPointerException are observed:

1 http-nio-8080-exec-17 ERROR anonymous 979x12x1 - 10.10.0.36,10.10.0.26 /secure/Dashboard.jspa [c.a.event.internal.AsynchronousAbleEventDispatcher] There was an exception thrown trying to dispatch event [RequestMetricsEvent{url=/secure/Dashboard.jspa, key=Optional[jira.dashboard], requestCorrelationId=Optional[d140ba27a1e6a2], reqTime=18, requestUserTime=10, requestCpuTime=10, requestGCDuration=0, requestGCCount=0, checkpointReachTime=[CheckpointTiming{checkpointName=serverRenderEnd, checkpointTime=PT0.015965215S}], activityTimings=[]}] from the invoker [com.atlassian.event.internal.ComparableListenerInvoker@585805f0] java.lang.RuntimeException: Listener: com.codebarrel.jira.plugin.automation.event.JiraIssueEventListenerImpl event: com.atlassian.jira.servermetrics.RequestMetricsEvent at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:49) at com.atlassian.diagnostics.internal.platform.monitor.event.EventSystemMonitor.invokeMonitored(EventSystemMonitor.java:105) at com.atlassian.diagnostics.internal.platform.monitor.event.MonitoredListenerInvoker.invoke(MonitoredListenerInvoker.java:38) at com.atlassian.event.internal.ComparableListenerInvoker.invoke(ComparableListenerInvoker.java:48) 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.diagnostics.internal.platform.monitor.event.MonitoredEventDispatcher.dispatch(MonitoredEventDispatcher.java:36) at com.atlassian.event.internal.EventPublisherImpl.publish(EventPublisherImpl.java:114) at com.atlassian.event.internal.LockFreeEventPublisher.publish(LockFreeEventPublisher.java:40) at java.base/java.util.Optional.ifPresent(Unknown Source) at com.atlassian.jira.servermetrics.RequestMetricsDispatcher.stopCollection(RequestMetricsDispatcher.java:77) at com.atlassian.jira.servermetrics.RequestMetricsDispatcher$CollectorHandle.close(RequestMetricsDispatcher.java:116) at com.atlassian.jira.servermetrics.MetricsCollectorFilter.doFilter(MetricsCollectorFilter.java:26) ... 25 filtered at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191) at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.base/java.lang.Thread.run(Unknown Source) Caused by: java.lang.NullPointerException at com.codebarrel.jira.plugin.automation.thirdparty.ThirdPartyComponentModuleTracker.getThirdPartyDescriptors(ThirdPartyComponentModuleTracker.java:45) at com.codebarrel.jira.plugin.automation.thirdparty.ThirdPartyComponentModuleTracker.getThirdPartyTriggers

The following errors can be seen in browser Console logs with 404 error code for GET request:

1 GET http://XXXXXXXXX:XXXX/XXX/s/-s6gy5/940003/1dlckms/9.1.6/_/download/resources/com.atlassian.streams.streams-jira-plugin:date-en-IN/date.js?callback=ActivityStreams.loadDateJs&_=1677760083878 404

Cause

  • The System Plugin could have been disabled.

  • Some module(s) disabled for Jira Activity Stream Plugin.

Solution

Ensure all the modules are enabled for the Jira (issues) in the JIRA Activity Stream Plugin.

  • To verify, Navigate to ⚙ > Manage apps > JIRA Activity Stream Plugin > Jira (issues) and confirm, ifmodules are Enable

Updated on March 21, 2025

Still need help?

The Atlassian Community is here for you.