We have configured our jobs to change the Build display name to match the PullRequest ID of the PR being run. This leads to multiple runs of the same PR having the same build display name. 

This feature has broken since version 1.30 (1.29 still works). The Junit trend graph is forever stuck at Loading since upgrading to v1.30 (I've even tried 1.43) and checking the Network panel in my browser I've tracked it down to a error 500 in the backend. The backend logs suggest that this is because the X-axis of the chart (since the move to e-charts requires unique build names).

However, setting a unique build display name fixes the issue. This can be verified by deleting all past runs of the job and adding the BUILD_NUMBER to the build display name so that multiple runs of the same PR still results in a unique build display name.

Requirement: The junit Trend graph should render successsfully even with duplicate build display names for past runs.