Test e-mail ticket creation.

[fire-bot]

Sent by Bastiaan Veelo (@veelo). Created by fire.

---

E-mail sent to coin-support@fire.fundersclub.com

-- Bastiaan.

[veelo]

Reply in GitHub.

[veelo]

Second reply.

[veelo]

Tagging @veelo.

[veelo]

@VolkerEnderlein can you please tag me in a new comment? Thanks.

[VolkerEnderlein]

@veelo This really looks very promising.

[veelo]

Well the ticket creation itself works, but I am not sure whether the comments end up in the reporter's e-mail inbox. When I created the ticket I got an email asking me to link my GitHub handle to my e-mail address. I held off of that for some time, and my replies did not come through. Then I did as I was asked, and my replies still did not come through. The first e-mail that came through was when you tagged me, and that may well be due to regular GitHub mechanics. I think GitHub filters out your own comments.

I think for this to work as we would want to, the reporter should receive comments by e-mail, without having to register his GitHub handle (if he even has one) with Fire. We can test this if you create a ticket this way (preferably from an account that is not associated with GitHub) but not registering your GitHub handle. Then I'll comment and we'll see if you get a reply.

But even if this works, I am not sure if it would still work if coin-support@coin3d.org would be configured to forward. Would the reply end up at the sender?

[VolkerEnderlein]

Yesterday I tried to use the registered address coin-support@fire.fundersclub.com to create a new ticket from an account not connected to github, but apparently this did not work as I do not see this issue. So this fire-bot seems to be a solution only for people connected to Github or a help for single individuals fastly creating issues in their github projects. I will ask the fire-bot team whether our scenario is known to work and how we should do the configuration on our side.