DOC-187 Fix a broken link to community guides (#6783)

diff --git a/server/sonar-docs/src/pages/analysis/external-issues.md b/server/sonar-docs/src/pages/analysis/external-issues.md
index b9c78e9b4ddc35b98d7ac31d6e738aa37712ca94..34fd4cecc0f33bec8d3f836104d1e552a378a9b0 100644 (file)
--- a/server/sonar-docs/src/pages/analysis/external-issues.md
+++ b/server/sonar-docs/src/pages/analysis/external-issues.md
@@ -7,7 +7,7 @@ This page lists analysis parameters related to the import of issues raised by ex
 
 SonarQube doesn't run your external analyzers or generate reports. It only imports pre-generated reports. Below you'll find language- and tool-specific analysis parameters for importing reports generated by external analyzers. 
 
-In the [Guides](https://community.sonarsource.com/c/announce/guides) category of the [SonarSource Community forum](https://community.sonarsource.com/) you might find instructions on generating these reports.
+In the [Guides](https://community.sonarsource.com/c/clean-code/guides/22) category of the [SonarSource Community forum](https://community.sonarsource.com/) you might find instructions on generating these reports.
 
 Some properties support the following wildcards in paths. The remarks for properties that support wildcards will mention that fact. If the remarks do not say wildcards are supported, then they are not.: