Continuing the discussion from Using discourse as a community ticket system…
The idea is creating an email-profile for whoever emails in (thus creating a topic) or is invited to participate to a topic.
- task: create profile without needing any authentication, the email-profile
Currently the predefined system user creates a topic for who emails in, and that topic isn’t associated to a person’s profile, even if they do create an account later on. That’s a very weird association there, if you ask me.
- task: associate emailed-in topic to email-profile
And if a person is invited to participate in a topic, currently they can’t reply to the email like a regular user would be able to. (on a side note, we also can’t invite an existing user, we can only @mention them and they should be notified, but I believe that might not always go as an email notification - I believe the invite button should work independent of person having an account)
I believe both problems could be solved by creating an email-profile in both cases (and improving the invite button). If the person emails in, email profile is already created. If they’re invited, the profile would be created once they accept it or reply to it. In fact, the invitation would be very different…
- task: allow reply to on invitation email
It would look like a mix of the current invitation and a topic notification, which includes the unsent parts of the topic. Also, right now once the invitation is accepted the person receives another email asking for them to create a password. I believe that link should be to “create a profile” and not a password necessarily, as they might prefer to use oAuth (passwords are a thing of the past!).
- task: add “topic notification” to invitation emails
- task: accepted invitation email should go through default profile creation process
I’m thinking in making an attempt at building this plugin / performing those tasks (and eventually 2 other ones later on), but I wanted to have some feedback first of what you guys think (and if any of you rather do it)!
I can see a lot of work for me there, mostly to get in the workflow, and I can also see some of the tasks shouldn’t be too much for whoever already is in the workflow, but above all I wanted to know if this idea makes sense or if it has any prohibiting unthought failure.
Striked above. I just can’t even consider trying to do it this year.
I should stop saying what I’m thinking in doing. I would love to have the time to make that effort, but I just realized I don’t. And I’ve managed to do basically everything I needed with discourse without any of the suggestions here.
I still think they would be quite valuable addendums and could convert much more people into using the tool. Eventually even learning how to upgrade their profile to really engage… All just guessing!
I do realize this might go against much of what Jeff considers is needed for engagement, but keep in mind the whole point here is extending discourse and allowing it to be used as a different kind of ticket system!
Few more tasks I just realized might be important, all about title restrictions:
task: allow email sent in to be unlisted by default
task: remove minimum length and allow duplicated titles for emails sent in, but makes it enforced unlisted
task: update warning email sent back with those new infos