Many of our clients use the Instance ID in the AMP reports to tie the violations in our reports to tickets in their own internal bug tracking systems (JIRA or otherwise). When reports are copied for regressions and validations, it is no longer possible for them to accurately identify and track violations by their Instance ID, since that changes with each copy.
The Instance ID that is generated when a violation is logged MUST persist in an identifiable way.
For example, a violation that has the ID 123456789 when is is initially logged should become 123456789-a when it is first copied. And each subsequent copy should see the appended alphabetic character changed while the original number remains the same. 123456789-b, 123456789-c, and so on.
This will allow clients to accurately identify and track issues as they pass through the initial audit, validation, and regression stages.