Totally agree! 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.
We have a Resubmission ID field for requirements published in legacy IGAM. We either need that field back for requirements in the new portal or some other type of flag on the requirement record indicating it's been republished, so we can search on it and possibly add it to a dashboard part.
Carol Greco
Totally agree! 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.
We have a Resubmission ID field for requirements published in legacy IGAM. We either need that field back for requirements in the new portal or some other type of flag on the requirement record indicating it's been republished, so we can search on it and possibly add it to a dashboard part.