Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Service desk feature #6219

Open
MartinDelille opened this issue Mar 1, 2019 · 1 comment
Open

Service desk feature #6219

MartinDelille opened this issue Mar 1, 2019 · 1 comment
Labels
kind/proposal

Comments

@MartinDelille
Copy link
Contributor

There is an awesome feature in Gitlab Enterprise Edition that I would love to see in Gitea called Service Desk: https://docs.gitlab.com/ee/user/project/service_desk.html

The idea is to manage the relation with your user throught issue that are created by email.
This was referenced Mar 1, 2019
Merged
Open
@JFronny
Copy link

JFronny commented Oct 22, 2022

Since no one has picked this up: I have implemented a naive version of this feature as a seperate service here, which you might be able to use in the meantime (no guarantees, though)

@KN4CK3R KN4CK3R mentioned this issue Dec 7, 2022
Merged
lunny added a commit that referenced this issue Jan 14, 2023
@KN4CK3R @silverwind @lunny
Add support for incoming emails (#22056)
fc037b4 
closes #13585
fixes #9067
fixes #2386
ref #6226
ref #6219
fixes #745

This PR adds support to process incoming emails to perform actions.
Currently I added handling of replies and unsubscribing from
issues/pulls. In contrast to #13585 the IMAP IDLE command is used
instead of polling which results (in my opinion 😉) in cleaner code.

Procedure:
- When sending an issue/pull reply email, a token is generated which is
present in the Reply-To and References header.
- IMAP IDLE waits until a new email arrives
- The token tells which action should be performed

A possible signature and/or reply gets stripped from the content.

I added a new service to the drone pipeline to test the receiving of
incoming mails. If we keep this in, we may test our outgoing emails too
in future.

Co-authored-by: silverwind <me@silverwind.io>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/proposal
Milestone
No milestone
Development

No branches or pull requests
3 participants
@lunny @MartinDelille @JFronny