Known issues in Jazz Foundation 7.2
The following issues and limitations are known for Jazz® Foundation 7.2 release. Some issues have workarounds, other issues are limitations.
Workarounds
The following issues in this release have workarounds.
- Intermittent widget loading failure on the Engineering Lifecycle Management mini‑dashboard
-
First occurrence: 7.0.2
ID: DT440594
Problem: Custom widgets hosted on server 1 intermittently fail to load in the Engineering Lifecycle Management mini-dashboard on server 2 when maintenance activities are performed on server 1. Maintenance can include deploying a new widget version, restarting the widget service, or other updates. During these windows users may see an empty window or the error CRJAZ5037E – The OpenSocial gadget was not loaded, and the problem can persist even after server 1 is back online, sometimes showing additional communication‑related errors. The only reliable remedy is to restart the Engineering Lifecycle Management application on server 2, which clears cached data and re‑establishes the widget‑Engineering Lifecycle Management connection.
Workaround: To prevent recurrence, coordinate widget maintenance windows with the Engineering Lifecycle Management administrators and perform a controlled restart of the Engineering Lifecycle Management application (or clear its cache) after any widget server change.
- Login redirects may be blocked when MFA is enabled
-
First occurrence: 7.0.2
Internal ID: 569767
Problem: When users sign in with Multi‑Factor Authentication (MFA), the sometimes encounter an error that says a “potential open‑redirect attack was detected.” This happens because the system changes part of the return URL during the login flow, causing the security check to fail. The problem only appears when MFA (or OIDC) is turned on, it does not occur with standard single‑sign‑on.
Workaround: Temporarily disable multi-factor authentication.
Limitations
The following issues in this release that does not have workarounds.
- Link lookup delays after a server rename
-
First occurrence: 7.0.2
ID: DT435006
Problem: When the server that stores project data is renamed, the system that retrieves linked information can take longer than the built‑in 15‑second limit to respond. As a result, users may see a timeout message and the linked data may not appear, causing interruptions in their workflow. To prevent this, avoid renaming servers in a live environment or schedule a controlled restart of the application after a rename so that the connections are refreshed.
- GC title truncation in history view
-
First occurrence: 7.0.3
ID: DT455800
Problem: The GC history view truncates titles that contain only underscores. As a result, a title such as
GC_with_a_very_long_title_that_does_not_fit_on_UIis cut off, while titles that include dashes or spaces wrap to the next line and remain fully visible. This incomplete display can confuse users and make it difficult to identify the correct change set or audit event. - Engineering Test Management Cluster Web UI Theme Not Propagated Across Nodes
-
First occurrence: 7.0.2
ID: DT378319
Problem: In Engineering Test Management clusters (minimum two nodes) a custom Web UI theme activated is applied only to the node where the change was made. As a result, inconsistent visual styling is applied when you log into different servers on the cluster, while other configuration changes (For example, advanced properties) continue to generate correctly across all nodes.
- Dashboard permissions available in Engineering Insights
-
First occurrence: 7.0.3
ID: DT118093
Problem: Dashboard permissions are not applicable for Engineering Insights, however, dashboard permission section is still available in the Engineering Insights admin page.
- Memory leak in DCM
-
First occurrence: 7.0.1
ID: DT256783
Problem: The items added to the cache are not removed. As a result, the expired item are not deleted from cache.