dev and doc feedback

Author: jc-berger

release_notes/known_issues_application.adoc

@@ -115,14 +115,14 @@ For deploying applications by using the pull model, the Argo CD controllers igno
 
 The `argocd.argoproj.io/skip-reconcile` annotation is only available in the GitOps operator version 1.9.0, or later. To prevent conflicts, wait until the hub cluster and all the managed clusters are upgraded to GitOps operator version 1.9.0 before implementing the pull model. 
 
-link:https://issues.redhat.com/browse/ACM-3910[ACM-3910]
+link:https://issues.redhat.com/browse/ACM-3404[ACM-3404]
 
 [#argo-pull-model-resource]
 == Resource fails to deploy
 
 All the resources listed in the `MulticlusterApplicationSetReport` are actually deployed on the managed clusters. If a resource fails to deploy, the resource is not included in the resource list, but the cause is listed in the error message.
 
-link:https://issues.redhat.com/browse/ACM-17819[ACM-17819]
+link:https://issues.redhat.com/browse/ACM-7843[7843]
 
 [#argo-pull-model-large]
 == Resource allocation might take several minutes
@@ -146,14 +146,14 @@ spec:
       requeueAfterSeconds: 0
 ----
 
-link:https://issues.redhat.com/browse/ACM-3910[ACM-3910]
+link:https://issues.redhat.com/browse/ACM-5177[ACM-5177]
 
 [#object-bucket-subscription-admin]
 == Application ObjectBucket channel type cannot use allow and deny lists
 
 You cannot specify allow and deny lists with ObjectBucket channel type in the `subscription-admin` role. In other channel types, the allow and deny lists in the subscription indicates which Kubernetes resources can be deployed, and which Kubernetes resources should not be deployed.
 
-link:https://github.com/stolostron/backlog/issues/22807[ACM-22807]
+link:https://github.com/stolostron/backlog/issues/22763[ACM-22763]
 
 [#changes-not-automatic]
 == Changes to the multicluster_operators_subscription image do not take effect automatically
@@ -162,7 +162,7 @@ The `application-manager` add-on that is running on the managed clusters is now
 
 If the image that is used by the subscription operator is overrided by changing the `multicluster_operators_subscription` image in the `multicluster-hub` image manifest ConfigMap, the `application-manager` add-on on the managed clusters does not use the new image until the subscription operator pod is restarted. You need to restart the pod.
 
-link:https://github.com/stolostron/backlog/issues/21446[ACM-21446]
+link:https://github.com/stolostron/backlog/issues/21013[ACM-21013]
 
 [#policy-needs-subscription-admin]
 == Policy resource not deployed unless by subscription administrator
@@ -173,7 +173,7 @@ A subscription administrator needs to deploy the application subscription to cha
 
 See link:../applications/allow_deny.adoc[Creating an allow and deny list as subscription administrator] for information. `policy.open-cluster-management.io/v1` resources that were deployed by existing application subscriptions in previous {acm-short} versions remain, but are no longer reconciled with the source repository unless the application subscriptions are deployed by a subscription administrator.
 
-link:https://github.com/stolostron/backlog/issues/17819[ACM-17819]
+link:https://issues.redhat.com/browse/ACM-893[ACM-893]
 
 [#application-ansible-standalone]
 == Application Ansible hook stand-alone mode
@@ -239,7 +239,7 @@ spec:
 
 After applying both, you should see the Ansible instance created in your hub cluster.
 
-link:https://github.com/stolostron/backlog/issues/8036[ACM-8036]
+link:https://bugzilla.redhat.com/show_bug.cgi?id=1908691[ACM-1908691]
 
 [#application-not-deployed-after-an-updated-placement-rule]
 == Application not deployed after an updated placement rule
@@ -296,7 +296,7 @@ apiVersion: security.openshift.io/v1
  - system:serviceaccount:my-operator:nginx-ingress-52edb-backend
 ----
 
-link:https://github.com/stolostron/backlog/issues/1764[ACM-1764]
+link:https://github.com/stolostron/backlog/issues/24248[ACM-24248]
 
 [#application-channels-require-unique-namespaces]
 == Application channels require unique namespaces
@@ -305,7 +305,7 @@ Creating more than one channel in the same namespace can cause errors with the h
 
 For instance, namespace `charts-v1` is used by the installer as a Helm type channel, so do not create any additional channels in `charts-v1`. Ensure that you create your channel in a unique namespace. All channels need an individual namespace, except GitHub channels, which can share a namespace with another GitHub channel.
 
-link:https://github.com/stolostron/backlog/issues/2311[ACM-2311]
+link:https://github.com/stolostron/backlog/issues/2160[ACM-2160]
 
 [#ansible-automation-platform-fail]
 == {aap-short} job fail