Documents for new issue by email

We have a great document for reply by email, and we should probably have another entry for new issue by email, or update the document accordingly to mention new issue by email.

The same instructions as here works and is required for setting up the new issue by email functionality: https://docs.gitlab.com/ce/administration/reply_by_email.html#email-sub-addressing

• the email address configured needs to include the '%{key}' placeholder for new issues by email to work
• You'd need access to the web UI for the first time to get access to that email address. it's a unique address per user to prevent spam.
• the email address is unique mainly due to that it's implemented with a special token belong to each person. since email address could be forged, we use that token to identify users rather than using the email address
• enabling reply by email is not necessarily to enable email-sub-addressing, but is needed if you want to create new issues from the email

We should also document the fact that sub-addressing is needed. Reference: https://gitlab.com/gitlab-org/gitlab-ce/issues/3243#note_21435217

mentioned in issue #3243 (closed)

added reply by email label

changed milestone to %8.17

assigned to @SeanPackham

changed milestone to %9.0

added docs-todo label

removed assignee

changed milestone to %9.1

added docs-missing label

Moving to %9.2 , but may be done in %9.1 depending on our load.

changed milestone to %9.2

mentioned in issue #31434 (closed)

changed milestone to %9.3

assigned to @axil

removed assignee

changed milestone to %9.4

changed milestone to %9.5

changed milestone to %10.0

Yeah there still seems to be doco missing for how to create new or update issues via email if your email provider doesn't support sub-addressing like !#@$#% office365 which is a real pain.

mentioned in issue #37382 (closed)

changed milestone to %Backlog

marked this issue as related to #38025

mentioned in issue #38025

moved to gitlab#7156

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 merge request !14785