We value your unique insight into our products and services and often receive ideas and feedback from our community in a variety of ways. To streamline this process, we’ve created an idea bank where you can post product suggestions, vote for those most important to you, and add comments to existing ideas.
We need to be able to reliably find Requirements where a resubmission has been requested.
When a resubmission is requested, an Activity History record is created. However, this is created against the Request, with no logic reference to the relevant Requirement (apart from the notes).
If a later Requirement is subsequently published for resubmission, it is not possible to find that requirement reliably as the Request now has multiple Activity History records for resubmission requests - we will get other requirements in our search for which there is no resubmission request.