drift@pvv email -> gitea issue automation #157

New Issue

pederbs · 2024-09-02T20:54:14+02:00

pederbs commented

2024-09-02 20:54:14 +02:00

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

👍 1

pederbs added the

labels 2024-09-02 20:54:14 +02:00

pederbs added this to the Kanban project 2024-09-02 20:54:14 +02:00

felixalb commented

2024-09-03 12:54:32 +02:00

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?

pederbs commented

2024-09-04 04:32:25 +02:00

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.

danio commented

2024-09-04 10:15:54 +02:00

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

oysteikt commented

2024-09-23 10:32:35 +02:00

Maybe this is duplicate-ish of #97?

oysteikt added the

mail

label 2024-12-08 00:56:20 +01:00

Sign in to join this conversation.

4 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Drift/issues#157