As per Fortify SSC specification, each issue should have a unique id across the whole scan. Because for multi-module projects, the exact same issue can appear under multiple modules - there might be a collision.
The solution was to use the filed displayTargetFile from the scan object, and prepend it to the existing unique issue id (hash of the issue json).
Also added a Target File field to the custom issue display, for convenience.
As per Fortify SSC specification, each issue should have a unique id across the whole scan. Because for multi-module projects, the exact same issue can appear under multiple modules - there might be a collision. The solution was to use the filed
displayTargetFilefrom the scan object, and prepend it to the existing unique issue id (hash of the issue json).Also added a
Target Filefield to the custom issue display, for convenience.