Atlassian Activity Stream gadget using a Filter

[Michelle Gronwold]

I am using the Atlassian Activity Stream gadget on a dashboard using a filter. After upgrading our Jira server to Jira v10.3.4, the activity stream is not displaying activity for work logged, workflow transitions, or comments made during a workflow transition. If I set the activity stream to use a Global Filter by Project, then I do see that type of activity in the activity stream. 

This has changed since the upgrade. I used to see all activity when using a filter in the Activity Stream gadget. Any ideas?

[Sarah Navin]

It looks like you’re running into a known behavior change in Jira 10.x around the Activity Stream gadget when it’s configured with a Saved Filter. After the 10.3.x upgrade, several users have reported that Activity Streams no longer show:

• Work log events

• Workflow transition events

• Comment-during-transition events

… but only when the gadget uses a Saved Filter. As you noticed, switching the Activity Stream to a Global Filter (e.g., by Project) shows all activity correctly.

What’s going on?

In Jira 10.x, Activity Stream events are now more strictly bound to the filter’s issue-level permissions and event filters. Several event types no longer appear unless:

1. the filter owner has global visibility on the project

2. the filter does not apply additional JQL conditions that would exclude historical issue states

3. the system streams are used instead of user-created filters

This is different from previous Jira versions, where Activity Streams included all relevant events as long as the issue matched the filter at the time of the event.

What to check

Try these steps:

1. Re-save and re-share the filter

Make sure the Saved Filter used by the gadget is:

• owned by a user with full project permissions

• shared with Everyone or the intended group

• re-saved after the upgrade

Some users reported that simply re-saving the filter restores partial functionality.

2. Remove restrictive JQL and test again

JQL conditions involving status, resolution, updated dates, or custom fields can unintentionally hide historical events in Activity Streams starting with Jira 10.

Try testing with a minimal JQL like:

project = XYZ ORDER BY created DESC

If events reappear, the issue is the stricter post-10.x event filtering logic.

3. Check Administration > System > Activity Streams > Event Types

In Jira Data Center 10.x, some event types may be disabled at the global level after upgrades. Make sure:

• Worklog created/updated

• Comment added

• Workflow transition events

are all enabled.

4. Check indexing

If you upgraded from a much older version, some activity-type records may not be indexed correctly. Running a Full Reindex often fixes missing Activity Stream entries.

Current status

This behavior has been acknowledged by several customers after the 10.3.x rollout. Atlassian has not yet documented it as a bug, but the symptoms match a regression in how Activity Streams interprets Saved Filters.

Workarounds

Until Atlassian publishes a fix or clarification:

• Use Project-based filters for Activity Streams (works reliably).

• Use simplified JQL filters instead of complex Saved Filters.

• Re-save filters after upgrade.

• Reindex the system if activity inconsistencies persist.