Skip to content
Snippets Groups Projects
Unverified Commit afed4b07 authored by anarcat's avatar anarcat
Browse files

you can now comment on any issue by email easily

parent 790e33cd
No related branches found
No related tags found
No related merge requests found
......@@ -126,27 +126,25 @@ description. You can use shortcuts in the body, like `/assign @foo`,
See [the upstream docs for more details](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#new-issue-via-url-with-prefilled-fields).
### Replying to an existing comment
### Commenting on an issue
If you just reply to the particular comment notification you received
by email, as you would reply to an email in a thread, that comment
will show up in the issue.
You need to have email notifications enabled for this to work, naturally.
You need to have email notifications enabled for this to work,
naturally.
See [the upstream docs for more details](https://docs.gitlab.com/ee/administration/reply_by_email.html).
### Creating a new comment
This is not easily doable right now (see: [issue 18816
upstream](https://gitlab.com/gitlab-org/gitlab/-/issues/18816)). However, if you have notifications enabled, you can
reply to any notification email of the issue by replacing everything
that would get quoted with the comment you want to add.
You can also add a new comment to any issue by copy-pasting the
issue-specific email address in the right sidebar (labeled "Issue
email", [introduced in GitLab 13.8](https://gitlab.com/gitlab-org/gitlab/-/issues/18816)).
This also works with shortcuts like `/estimate 1d` or `/spend
-1h`. Note: for those you won't get notification emails back, though,
while for others like `/assign @foo` you would.
See [the upstream docs for more details](https://docs.gitlab.com/ee/administration/reply_by_email.html).
### Quick status updates by email
There are a bunch of [quick actions](https://gitlab.torproject.org/help/user/project/quick_actions.md) available which are handy to
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment