Sorry to say but I think the answer is a feature request.
Please follow this link. You can use the link to report bugs and request new features.
The only solution I can think of meantime is a search for the image name as that would return anywhere on your PC the file is used. File Explorer would do it and there are some third party tools that are quicker. I use the freeware program Ultrasearch. If you download the zipped file, you can expand it to a thumb drive and run it from there without any installation.
See www.grainge.org for RoboHelp and Authoring information
Just thinking out loud on this a bit. Do the topics in question reside in the Resource Manager pod? I would think that some common location would be needed in order to fashion any kind of report on things like this.
Yes, the topics are in the Resource Manager Pod. They are also stored in a more or less common location (C:\Documentation\Work\Project[xyz])
I drafted how it looks like
In "Project X", I can see which topics are taken from another project and from which one. I'm looking for the information in "Install", that "File 1" is also used in "Project X".
Sorry for not having been clear. "Install Project X" and "Config Project X" are actually just folders in "Project X" containing files from the other projects ("Config" and "Install") in the Resource Manager.
Okay, just to see if I'm understanding this correctly. I personally just finished logging this bug with Adobe:
Here is the gist of what I reported:
Identifying projects using common Resource Manager assets
When using the Resource Manager pod and sharing assets between two or more different projects, there emerges a need to identify all the different projects that are using the assets.
Steps to Reproduce:
Add an asset to the Resource Manager. Open a different project and use the asset so it now exists in more than one project. Then update the asset so it needs to be changed in all projects using the asset.
The help author simply has to maintain some external list that can be referenced or just remember the projects so all the affected projects can be opened, update the asset, then recompiled or regenerated.
Hopefully I got that right.
As for your diagram, I've amended it slightly:
Thank you I already posted a feature request a couple of days before, but with a sligthly different requirement (https://tracker.adobe.com/#/view/RH-300). My initial idea was to see in my "Install" project (which is the source), that file 1 is also used in "Project X", "Project Y", etc. However, to see this information for all parts of the Resource Manager from anywhere inside the Resource Manager is also a nice idea.
Your amendment to the image isn't quite correct as for my initial description. All projects are stored under C:\RH\MyProjects, so even the one I'm editing right now (in the image "Project X") will be displayed in the Resource Manager, because there all content of the folder C:\RH\MyProjects is displayed. That's what I tried to show. Your amendment looks to me to be a mock up of the to-be solution?