OSSMDOC-354: Fix incorrect link in Release Notes.

JStickler · JStickler · commit e246fa34f232 · 2021-06-30T15:21:14.000-04:00
diff --git a/modules/ossm-rn-known-issues.adoc b/modules/ossm-rn-known-issues.adoc
@@ -36,7 +36,7 @@ These are the known issues in {ProductName}:
 
 * link:https://issues.jboss.org/browse/MAISTRA-1947[MAISTRA-1947] _Technology Preview_  Updates to ServiceMeshExtensions are not applied.  The workaround is to remove and recreate the ServiceMeshExtensions.
 
-* link:https://issues.jboss.org/browse/MAISTRA-1621[MAISTRA-1621]  _Migration to 2.0_  Prometheus scraping (`spec.addons.prometheus.scrape` set to `true`) does not work when mTLS is enabled.  Additionally, Kiali displays extraneous graph data when mTLS is disabled.
+* link:https://issues.jboss.org/browse/MAISTRA-1959[MAISTRA-1959] _Migration to 2.0_  Prometheus scraping (`spec.addons.prometheus.scrape` set to `true`) does not work when mTLS is enabled.  Additionally, Kiali displays extraneous graph data when mTLS is disabled.
 +
 This problem can be addressed by excluding port 15020 from proxy configuration, for example,
 +

Original file line number	Diff line number	Diff line change
`@@ -36,7 +36,7 @@ These are the known issues in {ProductName}:`
`36`	`36`
`37`	`37`	`* link:https://issues.jboss.org/browse/MAISTRA-1947[MAISTRA-1947] _Technology Preview_ Updates to ServiceMeshExtensions are not applied. The workaround is to remove and recreate the ServiceMeshExtensions.`
`38`	`38`
`39`		-* link:https://issues.jboss.org/browse/MAISTRA-1621[MAISTRA-1621] _Migration to 2.0_ Prometheus scraping (`spec.addons.prometheus.scrape` set to `true`) does not work when mTLS is enabled. Additionally, Kiali displays extraneous graph data when mTLS is disabled.
	`39`	+* link:https://issues.jboss.org/browse/MAISTRA-1959[MAISTRA-1959] _Migration to 2.0_ Prometheus scraping (`spec.addons.prometheus.scrape` set to `true`) does not work when mTLS is enabled. Additionally, Kiali displays extraneous graph data when mTLS is disabled.
`40`	`40`	`+`
`41`	`41`	`This problem can be addressed by excluding port 15020 from proxy configuration, for example,`
`42`	`42`	`+`