- there is a requirement item, that is linked to a member in source that cannot be handled as attachment.
- the linked member is the "major leading content" of the requirement, so the source trace field is set to the LIVE revision of the member; meaning that updates in source will be reflected in the requirement
- secondary items like test cases are linked to that requirement
When a new member revision is checked in, the source trace fields updates correctly, but there is no "suspect" flag in the related Test Cases.
A suspect flag is only set, if the User actively changes the sourcelink field in the requirement item.
There should be an event in the trigger api that could be cought an analysed in trigger scripts for the following scenario.