Allow custom support email without configuring custom project suffix
What does this MR do and why?
Right now, when a custom email address is used, users have to configure custom suffix for projects where they want to use the custom support email.
This MR changes that and when the custom email is configured, projects can use that configuration without the need to configure suffix. In that case, the email with the project identifier can be used.
Screenshots or screen recordings
How to set up and validate locally
- Configure incoming emails
- Configure custom support email
- Check project settings (eg. http://127.0.0.1:3000/flightjs/Flight/edit) - Service Desk section
- Try to send email to the address in the field and check if a new issue has been created (you can try the general incoming address, too)
- Add suffix in the service desk project settings and try the new address
Possible problems
There are problems with setting incoming emails. In order to make that working, need to update the MailRoom gem version in the Gemfile
, MR not merged yet:
- Cherry-pick the mailroom gem update
git cherry-pick 8103d700642bedf24ddd76bf03ccd895096284c5
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.
Related to #333916 (closed)
Edited by Jarka Košanová