Disable all notification emails

Description

We'd like to be able to disable all notification emails globally for a gitlab CE install.

Proposal

Links / references

Documentation blurb

Overview

What is it?

An admin flag to disable email notification for the entire installation.

Why should someone use this feature?

To set up global installation security. Similar to requiring 2FA for all accounts.

What is the underlying (business) problem?

We don't want any code or data going out over email.

How do you use this feature?

Use cases

Feature checklist

Make sure these are completed before closing the issue, with a link to the relevant commit.

• Feature assurance
• Documentation
• Added to features.yml

For some reason, I can't edit this issue, but I do want to say that we want to keep account verification emails and other account maintenance emails, which is why we just haven't removed the email server.

mentioned in issue #36079 (moved)

@icco Thanks for the proposal.

added Plan [DEPRECATED] ~14213 ~18332 ~160010 labels

It's definitely a feature that would be awesome.

It would also be useful to be able to disable all outgoing emails when debugging or experimenting with something in GitLab. Obviously this should be an admin-only function.

Definitely would be helpful to have.

@vadacom.benjamin-rood Outgoing emails from GitLab can be disabled completely:

• https://gitlab.com/gitlab-org/gitlab-ce/blob/91a3a4b526214f4174f4f12de23dfb5baf033211/config/gitlab.yml.example#L67

This issue refers to only notification email disablement, excluding account specific emails like confirmation and password resets etc. Currently, it's all or nothing.

This would be very useful, though I would want two variations also available:

• Disable notifications per-group
• Mask the content -- eg, send the email, but only say something like "An issue was filed at URL"

mentioned in merge request !19686 (closed)

I pushed !19686 (closed), it works locally in my development environment. It does what I need -- namely, the ability to disable notifications per-group or per-project. After some contemplating, I decided against masking the email content as that didn't really fit into my requirements.

Thinking about it, it would probably be fairly easy to extend my MR to work globally too. However, I've already spent more time on this than I was hoping to spend.

FWIW, we've been using !19686 (closed) on two gitlab 10.x installations since the beginning of July, and it has worked out great for us. Just need someone to review the MR and provide guidance for writing tests, then hopefully it can be introduced into mainline Gitlab.

@victorwu What do you think about this one? A Merge Request has been prepared

@smcgivern @jeremy_ : What do you think about this feature?

What do you think about this feature?

Comment moved to https://gitlab.com/gitlab-org/gitlab-ce/issues/50020

Let's not get off from the original request: disable email except account related ones (password reset, account verification, etc.). I think that satisfies @jeremy_'s UX requirements (clear radio silence). Current email flag disables password reset, etc., so isn't a solution.

Whoops, I thought I was posting this in the MR that's currently out (https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/19686) that does what I described.

Let's not get off from the original request: disable email except account related ones (password reset, account verification, etc.). I think that satisfies @jeremy_'s UX requirements (clear radio silence). Current email flag disables password reset, etc., so isn't a solution.

I agree. My comments were directed at that MR, which opts for selective disabling of notifications on a project/group basis. In my view, we shouldn't do this.

Sorry for the confusion @jeremy_ . I created a separate issue that matches the MR. Can you please paste your comment on that new issue?

It is here; https://gitlab.com/gitlab-org/gitlab-ce/issues/50020

mentioned in issue #50020 (moved)

Thanks a million for the new issue. My fault for not noticing this issue and the MR were a bit different to one another

Any update for this?

added devopsplan label

added [deprecated] Accepting merge requests label

added groupproject management label

removed [deprecated] Accepting merge requests label

added auto updated potential proposal labels

Hey!

GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current gitlab-ce repository will become a read-only mirror, without any proprietary code. All development is moved to the current gitlab-ee repository, which we will rename to just gitlab in the coming weeks. As part of this migration, issues will be moved to the current gitlab-ee project.

If you have any questions about all of this, please ask them in our dedicated FAQ issue.

https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

You can also find more information here:

• https://gitlab.com/gitlab-org/gitlab-ee/issues/13304
• https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/

Frequently Asked Questions

For an up to date list of questions and answers, please take a look at https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

What will we do with the repository names?

https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.

Why rename gitlab-ce to gitlab-foss?

Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear

I created a merge requests for CE, and this got closed. What do I need to do?

You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.

How does the licensing work in this new setup?

Everything in the ee/ directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in the ee/ directory, the process of contributing changes is the same as when using the gitlab-ce repository.

Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?

No. Merge requests submitted to this project will be closed automatically.

Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?

Yes.

How will this affect users of GitLab CE using Omnibus?

No changes will be necessary, as the packages built remain the same.

How will this affect users of GitLab CE that build from source?

Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.

Where can I see a timeline of the remaining steps?

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304

Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?

Yes, these changes will be synced to gitlab-foss automatically, several times per day.

locked this issue

mentioned in issue gitlab#370454 (closed)