Issue Summary

After upgrading to Jira Data Center 11.3.x, the "Recently Created Chart" gadget fails to update its display when a user edits the gadget to select a new filter. While the edit dialog shows the correct selection, the chart continues to render old data or remains empty. Technical analysis shows that the gadget save action correctly updates the id and type fields, but fails to populate the projectOrFilterId field, which the renderer relies on.

Steps to Reproduce

1. Upgrade Jira Data Center to version 11.3.7.

1. Add a "Recently Created Chart" gadget to a dashboard.

1. Edit the gadget and select a saved filter (e.g., Filter A). Save the gadget.

1. Edit the gadget again and change the selection to a different filter (e.g., Filter B).

1. Observe the gadget display.

Expected Results

The gadget should refresh and display the chart based on the data from Filter B.

 

Actual Results

The gadget continues to display data from Filter A (or no data if it was a new gadget). A full page refresh is required to see the change, but the underlying preference mapping remains inconsistent.

A review of the gadget preferences via /rest/dashboards/1.0/<dashboardId>/gadget/<gadgetId>/prefs reveals a disconnect:

• The id field correctly reflects the new filter ID (e.g., 91801).

• The type field correctly reflects filter.

• The projectOrFilterId field remains empty ("").

Because the Jira 11 gadget renderer specifically looks for the projectOrFilterId value to fetch chart data, the chart fails to update because this field is never written during the save operation.

JSON Evidence (from /prefs endpoint):
 {{

{ "name": "projectOrFilterId", "value": "", "type": "hidden"}

,

{ "name": "id", "value": "91801", "type": "hidden"}

,

{ "name": "type", "value": "filter", "type": "hidden"}

}}
 

Workaround

Standard UI workarounds (full page refresh, clearing browser cache) have been reported as ineffective by the customer but working locally. The gadget remains in a broken state because the projectOrFilterId preference is never successfully written to the database during the save operation.

 

Note: This is affecting Jira 11.3.7 but I was not able to select it during this ticket creation