tknospdr
(David Muszynski)
5. September 2025 um 20:25
1
I’ve been working on a replacement for our company’s ticketing system using Discourse.
I know it has a lot of built in reports, but I’m not sure what is germane. Is anyone here using the software in that way already able to offer a list of reports that show the type of information that a dedicated solution like ZenDesk would have?
merefield
(Robert)
5. September 2025 um 23:21
2
Be sure to check out my workflow system:
Which has an audit report and a workflow state report out of the box.
1 „Gefällt mir“
(Not really reports, but is kind of related)
See:
Repo
Summary
This plugin adds a ticketing system to Discourse. It requires tagging to be enabled and works best alongside the Assign Plugin .
It is based on @tobiaseigen ’s original spec , and has been built in collaboration with @tobiaseigen and an awesome Ruby for Good team , for the benefit of both Namati and the Discourse community.
Notes
When you install the plugin, three new tag groups are added tickets_priority, tickets_reason and tickets_status. Add tags to these groups (at /tag_group…
I know there are other topics here floating around about using discourse as a ticket system, but I thought I’d start a fresh one to give a fairly complete picture of how we think discourse can be used with the current functionality, known issues, and what fixes/new functionality might help. This might also be faq material. Would be psyched to discuss with others trying to do the same thing and any workarounds you’ve found that I am missing so far.
Also quite pleased to discover a whole genre of…