I understand we should probably not use discourse for this, but what if I want a new kind of “community open” ticket system? Can you picture any deal breaker issues with this?
Also, is there maybe someone else who tried to do anything similar?
Without any extensibility, this is how I envision it might work right away, for our little business:
- We’d slowly and even personally warn users of how it works. They’re already used with our different thinking methodology anyway.
- Anyone would be able to comment on other people’s tickets.
- You’re responsible for tracking (getting updates on) your own ticket if you want.
- Staff would need to manually give the topic link for each new ticket associated with the corresponding customer, at least for new users.
Maybe a few issues, but not so terrible given the concept:
- You can’t have an automated list of your own tickets in the site (as already implied, unless you bookmark / star them yourself).
- No user sensitive information must be shared on the site (not like facebook is all that much safer, if you know what I mean).
I would guess it shouldn’t be too hard to extend it to make it more private and thus “covering” those issues:
- Make new topics invisible per default in a specific category.
- Let users list invisible topics to which they’re assigned or simply “have read”.
- Pre-assign emails to topics, so new users can have their own invisible topics list.
It wouldn’t be a “community ticket system” any longer, but it’d still be a great tool IMHO.
Instead, I’m really into the whole idea of opening the tickets and see what happens!
Man am I excited about this?
There must be a huge problem I’m over seeing here…