Add latest changes from gitlab-org/gitlab@14-6-stable-eev14.6.0-rc42

1 files changed, 6 insertions, 1 deletions

diff --git a/doc/user/project/service_desk.md b/doc/user/project/service_desk.md
index 4f8e068ca2d..072d685bde4 100644
--- a/doc/user/project/service_desk.md
+++ b/doc/user/project/service_desk.md
@@ -274,7 +274,7 @@ When configured, the custom suffix creates a new Service Desk email address, con
 
 For example, suppose the `mygroup/myproject` project Service Desk settings has the following configured:
 
-- Project name suffix is set to `support`.
+- Email address suffix is set to `support`.
 - Service Desk email address is configured to `contact+%{key}@example.com`.
 
 The Service Desk email address for this project is: `contact+mygroup-myproject-support@example.com`.
@@ -289,6 +289,8 @@ In these issues, you can also see our friendly neighborhood [Support Bot](#suppo
 
 ### As an end user (issue creator)
 
+> Support for additional email headers [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/346600) in GitLab 14.6.
+> In earlier versions, the Service Desk email address had to be in the "To" field.
 To create a Service Desk issue, an end user does not need to know anything about
 the GitLab instance. They just send an email to the address they are given, and
 receive an email back confirming receipt:
@@ -304,6 +306,9 @@ are sent as emails:
 
 Any responses they send via email are displayed in the issue itself.
 
+For information about headers used for treating email, see
+[the incoming email documentation](../../administration/incoming_email.md#accepted-headers).
+
 ### As a responder to the issue
 
 For responders to the issue, everything works just like other GitLab issues.