re-add the KI for RHID-3931

Signed-off-by: Nick Boldt <[email protected]>

Author: nickboldt

assemblies/assembly-release-notes-known-issues.adoc

@@ -10,9 +10,9 @@ include::modules/release-notes/snip-known-issue-rhidp-4378.adoc[leveloffset=+1]
 
 include::modules/release-notes/snip-known-issue-rhidp-4067.adoc[leveloffset=+1]
 
+# fixed in 1.4,  present in 1.3
+include::modules/release-notes/snip-known-issue-rhidp-3931.adoc[leveloffset=+1]
 
+# fixed in 1.5, present in 1.3
 include::modules/release-notes/snip-known-issue-rhidp-3396.adoc[leveloffset=+1]
 
-
-include::modules/release-notes/snip-known-issue-rhidp-3931.adoc[leveloffset=+1]
-

modules/release-notes/snip-known-issue-rhidp-3931.adoc

@@ -0,0 +1,10 @@
+[id="known-issue-rhidp-3931"]
+= Entities of repositories under a configured org in catalog-backend-module-github-org plugin are not deleted from the catalog when the imported repository is deleted from bulk imports
+
+Repositories might be added to Developer Hub from various sources (like statically in an app-config file or dynamically when enabling GitHub discovery). By design, the bulk import plugin will only track repositories that are accessible from the configured GitHub integrations.
+When both the Bulk Import and the GitHub Discovery plugins are enabled, the repositories the latter discovers might be listed in the Bulk Import pages.
+However, attempting to delete a repository added by the discovery plugin from the Bulk Import Jobs may have no effect, as any entities registered from this repository might still be present in the Developer Hub catalog.
+There is unfortunately no known workaround yet.
+
+.Additional resources
+* link:https://issues.redhat.com/browse/RHIDP-3931[RHIDP-3931]