The legend for a Bar Chart widget within a Status Report fails to display on the main dashboard view when the data is filtered to a single attribute value
Steps to Reproduce:
In the Modern UX (MUX), navigate to a project and access the Status module, click Configure, and select Add Bar Chart.
Configure the widget properties as follows:
Title: Cost
Target Object: Financials – Cost Plan Details
Type: Sum
Format: Number
Group By: Transaction Class
Sum: Actual Cost; Budget; Forecast
Apply the following additional configurations:
Sort Order: Descending
Bar Orientation: Horizontal
Group Format: Clustered
Under the “Only include items where…” filter section, add the following:
Transaction Class: Internal Labor
Plan of Record: Yes
Save the widget configuration and click Done.
Navigate to the newly created Bar Chart widget on the Status Report:
Observe that the legend (Budget, Actual Cost, Forecast) is not displayed.
Expand the Bar Chart widget and note that the legend appears at the bottom.
Modify the filter to include an additional Transaction Class:
Transaction Class: Internal Labor; Maintenance
Plan of Record: Yes
Save the changes and click Done.
Observe the updated results:
The legend (Budget, Actual Cost, Forecast) is now displayed on the widget and renders correctly in the Status Report PDF.
Remove either "Internal Labor" or "Maintenance" from the filter set:
The legend disappears from the widget view.
The legend remains visible only when the Bar Chart widget is expanded.
Expected Results: The bar chart legend should consistently display on the widget and in the Status Report PDF regardless of the number of values selected in the filter.
Actual Results: The legend is hidden on the widget when a single filter value is applied, though it remains available in the expanded view.
Clarity 16.4.1
DE184091
Following a technical assessment on DE184091, it has been determined that the legend display behaviour is functioning as intended. A fix will not be implemented for this use case, as forcing to display legend in constrained spaces causes user interface regressions.
In smaller containers, forcing a Highcharts legend can result in data overlaps and a degradation of usability. To maintain optimal readability and ensure the widget remains functional, the legend is dynamically rendered only when specific architectural thresholds are met.
The legend will appear on the canvas only if both of the following conditions are satisfied:
Maintaining these thresholds ensures the widget remains functional and visually clear for the end user.