Adds custom email capability to projects service_desk_address
What does this MR do and why?
Project
has accessors for service_desk_incoming_address
and service_desk_custom_address
for Service Desk addresses generated from incoming_email
and service_desk_email
. There is also service_desk_address
that returns the "most custom" address.
Because we're about to release real custom email addresses for Service Desk in Beta soo, we need to rework this and allow service_desk_address
to return the real custom email address.
This MR introduces the following:
- Rename
service_desk_custom_address
toservice_desk_alias_address
(naming like in the updated documentation) - Add new
service_desk_custom_address
that returns the real custom email address, if defined and enabled. - Let
service_desk_address
also return the custom email address. Use this order:- custom email
- address generated from
service_desk_email
- address generated from
incoming_email
Glossary
incoming_email
: An email address that is used for adding comments and issues via email. When you reply on a GitLab notification of an issue comment, this response email will go to the configured incoming_email
mailbox, read via mail_room
and processed by GitLab. You can also use this address as a Service Desk email address. The configuration is per instance and needs full IMAP or Microsoft Graph API credentials to access the mailbox.
service_desk_email
: Additional email address that is only used for Service Desk. Only works as an entry point for new tickets. Replies etc. will be handled using incoming_address
. Service Desk works without setting up configuration for this.
Screenshots or screen recordings
How to set up and validate locally
Please reach out, if you'd like to have steps for local validation
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.