I will say that the Solved plugin and Assign plugin help a lot. If a bug is reported for example, the admin assigns it. If it is solved, then the solved would auto close the topic after 24 hours. The solved shows a check mark next to the topic in the topic list.
Rather, the only purpose of the tickets plugin in this case is that it creates 3 tag groups - ticket priority, ticket status, and ticket reason. We can create tag groups also without plugins. I think this is more of a convenience to see all topics associated with a ticket from the admin panel.
If you use the tag icons theme component, you can color your tags and add a ticket icon for it as well, with tags that you created without the plugin.
Maybe @meglio asked this for the same reason: Weāre trying to setup Discourse for our companies internal communication and organisation. Therefore weād like to employ the ticket plugin for task management but encounter the problem, that everyone has to become a staff member to view the ticket dashboard. (And making everyone moderator or admin brings a lot of other workaround and customisation questions for us).
So, if there isnāt already a possibility to get the ticket dashboard viewable for every user, is it maybe planned to have this - maybe in regards of the development of Discourse for Teams?
@jerry0 Thanks for the nudge, Iāve updated the OP.
Generally, if youāre interested in this plugin I would encourage you to check out Discourse for Teams. I donāt work for Discourse.org, and Iām not entirely sure if you could fulfil this use case within that framework, but if I were considering a use case involving this plugin, Iād start by looking there. I would note that the original author of the spec for this plugin @tobiaseigen now works for Discourse.org (perhaps even on Discourse for Teams?)
That said, if you are interested in taking this plugin further, Pavilion would be open to developing it as part of a paid contract, depending on what youāre looking to do. You can PM @Ellibereth if youāre interested in doing that. Weād also potentially be interested in doing some (free) open source work on it, but our schedules in that respect are currently very full, so itād have to be later in the year.
We (Pavilion) donāt currently use this plugin internally. If that changes, and we start using it for some reason, then you may see some work on it sooner (@Ellibereth perhaps we should; letās revisit this).
@angus I just started using Tickets today, and immediately am faced with errors/bugs. The Assign plugin was just updated today, so I wonder if that is related?
When I add tags, i get a message āSorry, an error has occurredā If I submit the tags again, they seem to succeed. But the assign/unassign button doesnāt seem to work at all. In fact, it seems to interfere with the assign/unassign button from the Assign plugin.
There are various errors that pop up in the console.
And here are screenshots of the Assign and Tickets dashboards. You can see that Tickets isnāt recognizing assignments.
Putting aside the bugs I reported above, on further inspection, Iām not sure that I can use Tickets. Thereās various feature requests that have been mentioned that would be very useful, but my primary roadblock is that it can only really be used by staff members. I want to use this for an open-source project to allow volunteers to better self-organize their efforts, but donāt want to give them unnecessary permissions. I assume that if it was opened to other user trust levels, the tickets dashboard would also become available to them as well.
This has been mentioned a few times through this thread, most recently by @matenauta and @m4ur1c3 here Tickets Plugin š - #155 by renguer0. I concur with them that not only would it be very useful, but it also would be more in-line with the philosophy of Discourse, Pavilion, and presumably even the project that this was initially sponsored for.
Iāll likely do as others have pointed out and just use Assign with my own tag groups. It would be nice to have those buttons though and a functional ticket dashboard that is viewable and filterable by all.
Hi @angus I second that - we also recently noticed that we are now missing the Assigned column information (even though all tickets have been assigned):
@jerry0 Glad to see that Iām not alone/crazy! Do you have the other bugs/errors shown in my screen recording that happen when trying to add the Ticket tags or assign a topic through the Ticket interface?
Guys be aware of our support policy. We will have to see if we have the resources to fix this before month end. Unfortunately this is not one of our core plugins so will be discretionary.
We are looking to improve the monetisation of our plugins to better ensure resources for timely support
I assume that the resources to fix this before month end were not there but I hope that itās still within the support policy will mean that this is looked at in the first five days of December - just checking as itās now 3rd so wanted to give you a heads up.
@Ellibereth you feel that this support is something that needs payment for please say!
Hey @angus, Iām just wondering if youāve been able to make any progress with this? Iām looking to set up a workflow soon for my community and really would love to use Discourse Tickets! Any estimate of when we might see an updated version? Thanks for all your hard work and contributions to the community!
