I am having an additional similar issue though. I can’t seem to use the ticketing plugin with private messages.
The ticket button appears but I can’t select priority, status or reason. I enabled tagging for private messages in my discourse settings.
Edit:
I believe there is a bug with the “tickets include group” setting. Leaving it blank solved the above issue. It may have been because the group was already assigned.
Cool! I have been having this same issue since a recent update to discourse. I have now made this setting blank so will see what happens. I did notice that by manually inviting that group to the message brings the ticket tag pulldowns back to life.
As regards @foohonpie feedback… thanks for it! It’s always good to have more people try it and give feedback on the experience.
I don’t share your requirement that tickets be assigned to more than one person at a time, and that (along with your attempts to make it fit your requirement) seems to be a source of all of your assignment woes. Also all of your “Integration was both good and bad” feedback.
As regards your “Other minor issues” feedback - I agree with you here. The interface for viewing and filtering tickets needs a review, both because it is buggy and because maybe there is a better way to do it. I’ve suggested some next steps above. Would love to hear input on those suggestions, or offers to help!
This is a known issue that I do hope @angus prioritizes. Also mentioned above.
Thanks for the update! Also btw, I should mention regarding this:
I’ve since discovered that we can mute specific categories, which would have solved this problem entirely.
Humorously enough (because laughing saves me from crying ) the external tool we switched to, for as nice as it was, became a ghost town just as I feared. I may give this one another go with a change in approach this time around.
It turns out, a good tool that gets used may be better than a better tool that doesn’t.
Thanks @angus … apologies for the silly questions but how does one do a “normal API” request like the one in your screenshot? In my “edit topic” I don’t see the Ticket, Priority, Status or Reason? The “Unassign” also seems to be different in my setup?
Thanks for the detailed instructions!
I still hope to use this plugin someday as an option to provide support to my customers (users) - that they would be able to open a support ticket in some way.
Looks to me like you need to enable the plugin. Are you sure you followed all the steps correctly to install it?
It’s alot of fun! Here’s a screenshot to get you on your way. Note the is_ticket to enable the ticket and that you need a tags[] for each tag you want to add. Also, note that to assign tickets via the API you need to do a follow-up call which I have not figured out how to do via postman.
maybe there’s a conflict with another plugin? can you try disabling the voting plugin temporarily and see if you see the TICKET button when editing a topic title?
Aside - I’ve just been nudged that it’s time for you and I to get a room. If this still doesn’t get you on your way and you still need help with getting the ticket button showing up when editing topic title, please PM me.
Consider replying to more people
You’ve already replied 3 times to @GeertClaes in this particular topic.
Have you considered replying to other people in the discussion, too? A great discussion involves many voices and perspectives.
I thought I’d share my solution for others in the future. I had assumed that the fact that the Tickets Plugin shows up as “Enabled” in Plugins it meant that the tickets plugin is enabled. However, it appears that there is another “Enable tickets on topics?” setting. Maybe an idea to add this to the notes above?
OK, I have edited the OP with my wishlist, consolidating info from various places where we’ve talked about it. Feel free to scale back ambitions or reorganize as you see fit.
I updated the notes in the OP to hopefully address this concern. Let me know if you think my fix is good enough or feel free to improve further.