Improved filtering of "module" tags after ReqIF import

We receive requirements from our customer as a ReqIF format.  When importing, we have to check to see if any previously sent requirements in our DNG project have been removed in the incoming ReqIF file. This is the only way that we know that our customer has deleted a requirement from the project. Luckily, the ReqIF import utility in DNG provides an option to "tag artifacts that are present in repository modules being updated, but are not present in the package" (see attached screenshot). This method allows for deleted requirements to be "tagged" so that we can find them in the database.

The problem is that the tags that are applied to the artifacts are done in the "module" context and are not applied to the base artifact. These module tags are only visible from within the specific requirements module. This means that once the import is finished, we have to look in each requirements module separately and manually (and more prone to mistakes!) to determine if any requirements were deleted. There is no way that we have found to filter through all project artifacts across all modules to see which requirements have the "deleted" module tag. When the customer project has 50+ modules, the process of find out if any requirements were deleted can take a very long time. If the tags were applied to the base artifact, for example, then filtering in the artifact context would be simple and quick.

Potential Options:
- Create tags during the ReqIF import process in the "base artifact" context instead of in the "module" context.
- Allow for more options to edit existing tags. From the "manage tags" dialog box, give the user the option to change the context of the tag, for example from a "module" tag to a "base artifact" tag.
- Expand the display and filtering capabilities in the module context to allow filtering across multiple modules.
- Expand the ReqIF import process to include a screen that displays all "artifacts that are present in repository modules being updated, but are not present in the package" and gives the user options to tag, edit fields, etc. to better identify the deleted requirements after the import.

Thanks for your consideration! Please feel free to reach out for any specific questions or clarification that might be needed.