drift@pvv email -> gitea issue automation #157

Open
opened 2024-09-02 20:54:14 +02:00 by pederbs · 4 comments
Owner

Is it too much spam, or is this a good idea? Perhaps a human-in-the-loop system where we approve which emails to turn into issues

Is it too much spam, or is this a good idea? Perhaps a human-in-the-loop system where we approve which emails to turn into issues
pederbs added the
gitea
enhancement
question
exploration
labels 2024-09-02 20:54:14 +02:00
pederbs added this to the Kanban project 2024-09-02 20:54:14 +02:00
Owner

As a user seeking support from drift, I would not appreciate if my ticket was made public to everyone on the internet, so it would at least have to be a separate and private board, not this one. Also, there are other, good, ticketing systems to manage user support. I tried running all the drift-emails into osTicket a year or two ago, and wasn't really happy with it. However, rt seems good, maybe we could try that?

As a user seeking support from drift, I would _not_ appreciate if my ticket was made public to everyone on the internet, so it would at least have to be a separate and private board, not this one. Also, there are other, good, ticketing systems to manage user support. I tried running all the drift-emails into osTicket a year or two ago, and wasn't really happy with it. However, `rt` seems good, maybe we could try that?
Author
Owner

anything that supports us coordinating and tracking the response would be nice. Too often do we fail to reply-all when responding to emails. I was imagining using the "incoming email" feature in gitea to basically turn the resulting issue into an email thread.

anything that supports us coordinating and tracking the response would be nice. Too often do we fail to reply-all when responding to emails. I was imagining using the "incoming email" feature in gitea to basically turn the resulting issue into an email thread.
Owner

We have talked about doing it in matrix before (lol)

We have talked about doing it in matrix before (lol)
Owner

Maybe this is duplicate-ish of #97?

Maybe this is duplicate-ish of #97?
Sign in to join this conversation.
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Drift/issues#157
No description provided.