Cannot `/unsubscribe` from a (merged) MR with quick actions via email and comment

I tried to unsubscribe from an already merged request (!6024 (merged)) with slash commands and failed.

Preconditions:

• subscribed by pressing the thumb-up button,
• when the MR was not merged yet,
• didn't make any other actions, didn't change subscription status

Then, when I got a mail notification about the merge:

1. Opened the link in email and unsubscribed
2. Subscribed back to test unsubscription by email
3. Replied to the email with /unsubscribe in it.
4. Either reloaded the same page or opened the link again, don't remember that exactly.
   • The email body was posted as a comment having the same text.
   • The email also had a "footer" part with "Best regards, blabla..." and the citation of notification email but it was cut out.
   • Subscription status didn't change, the button text said "Unsubscribe".
5. Tried to edit and re-submit the same comment with no effect.
6. Posted a new comment with /unsubscribe. Same result, another comment posted.

I'm still able to unsubscribe and subscribe back with a button.

I was able to /unsubscribefrom that MR. Maybe I had to be subscribed before merge?

The slash commands don't currently force an update of the sidebar UI so after you enter it, could you try refreshing and see if you unsubscribe?

Although I can see your slash commands have been entered as notes which I think is a strong indicator that they weren't registered as slash commands.

Added ~12980 ~584040 labels

@lbennett Yes, I know that the page doesn't update after subscription (and I've posted it as an issue #21361 (moved)). But I reloaded the page after every attempt and the text on the subscription button didn't change. I take that as an indicator, but it is indeed possible that I actually did unsubscribe, but the button didn't update.

@lbennett I've updated the issue with more details, hope this will help.

@lbennett happened again in an open MR: https://gitlab.com/gitlab-org/gitlab-ce/issues/21624#note_14703135

Added ~874211 label

changed title from Cannot /unsubscribe from a (merged) MR with slash commands via email and comment. to Cannot {+/unsubscribe from a (merged) MR with quick actions via email and comment+}

moved to gitlab#6013

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