From 47a13038a4e280cd71ee77ad83af523d83d31279 Mon Sep 17 00:00:00 2001
From: Michael Telatynski <7t3chguy@gmail.com>
Date: Wed, 25 Oct 2023 11:06:53 +0100
Subject: [PATCH] Document `feedback.new_issue_url` &
 `feedback.existing_issues_url`

Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
---
 docs/config.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/config.md b/docs/config.md
index 6a2a59fc5ac..0f59e8ba375 100644
--- a/docs/config.md
+++ b/docs/config.md
@@ -355,6 +355,8 @@ If you run your own rageshake server to collect bug reports, the following optio
 2. `uisi_autorageshake_app`: If a user has enabled the "automatically send debug logs on decryption errors" flag, this option will be sent
    alongside the rageshake so the rageshake server can filter them by app name. By default, this will be `element-auto-uisi`
    (in contrast to other rageshakes submitted by the app, which use `element-web`).
+3. `existing_issues_url`: URL for where to find existing issues.
+4. `new_issue_url`: URL for where to sub\*\*\*\*mit new issues.
 
 If you would like to use [Sentry](https://sentry.io/) for rageshake data, add a `sentry` object to your config with the following values: