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!
A problem has been reported with the Tickets plugin and it’s unfortunately currently marked as a #plugin:broken-plugin. If you remove the plugin from your app.yml and rebuild it should allow the rest of the site to use tags as normal.
(I’ve moved these posts across to the Tickets topic so they can better track the issue )
Thanks VERY much for your work on this! I really hope that it can get polished off soon!
I have done some basic testing now and it is still having most of the problems that I reported here.
I no longer get the popup error message saying “Sorry an error has occured”, but clicking the Assign button in the Tickets module (to the right of the tags) doesnt do anything and produces the same console errors shown previously in the screen recording.
I can assign a topic with the Assign button below the topic, but Tickets and Assign still don’t seem to be talking to each other. The Assigned column in the Tickets Dashboard doesn’t populate.
Also, I’m hoping that while you are looking at this you might be able to give a bit of attention to the request that a variety of people have made - allowing groups beyond “Staff” to be able to use Tickets. I poked around in the code a bit and noticed a few places where it says things like currentUser.staff, is_staff etc… So I’m guessing that it wouldn’t be too difficult to either
relax/remove that stipulation,
add another userGroup (e.g. TicketsTeam) that we could create and define ourselves, or
add some sort of customization mechanism in the Tickets settings that allows us to define which groups have access to Tickets.
Obviously 3 > 2 > 1, but whatever you are inclined towards would be greatly appreciated! I also think it would make Tickets more broadly appealing, which would make your previous hard work more worth the while.
However I still consider this plugin to be broken as none of the interplay with the Assigned plugin is working any more, and both @Nick_Chomey and me have been reporting this (and contacting Pavilion separately for months without any useful response). It just doesn’t show who a ticket is assigned to which is pretty major issue.
Sorry if we’ve missed your messages! How did you try and contact us? Did you file a bug report (I don’t see any for the tickets plugin)? Did you message me somewhere? Or do you mean your posts earlier in this topic?
Given the tags issue is confirmed as fixed, and I’ve addressed the assign integration, I’ll be moving this back to #plugin.
Hi Angus - I really appreciate you working on this. That’s fantastic!!! (and in response to your question, I PM’d @ellibereth a few times as you suggested in your post above). Sorry, I didn’t file a bug report but note that for the future!!
@angus Thanks for the further work on this. I get this error when I go to site.com/admin/tickets
It goes away if I check Redirect user assigned routes to ticket dashboard.
Also, I think @jerry0 was referrring to our various tagged replies here over the past 6 months… I think we thought those were sufficient, given that you and your team had acknowledged the problems on a few occasions…
If only there were a Tickets mechanism here that non-staff members had access to, then it would be easy for a group of unrelated people to track and manage communal tasks …
It is something that is desperately needed in a decentralized community, such as those often run on Discourse. It doesn’t make sense to use a separate project management tool (off-site friction, costs and overkill), not all issues warrant being made/tracked on Github (off-site friction, non-code-related issues/tasks, etc…), and, obviously, such a task needs more than just a category of topics (hence the existence of this plugin).
It is already possible to use the Assign Plugin to assign topics to non-staff members (such as those within a particular group) - it seems only natural (and, I suspect, not terribly difficult) to extend such functionality/access to the Tickets plugin. I’d do it myself, but I don’t really know how Discourse development works… It would take me days to figure out.
So, I really hope you can take a quick look into modifying Tickets in one of the ways suggested in my previous post. A final thought on it - given that non-staff don’t have access to site.com/admin perhaps the tickets dashboard can/should be moved to the User Dashboard, where the Assigned Dashboard is e.g. site.com/u/[username]/activity/tickets
So just to confirm, everything (including the assign integration) is working as expected for you, if tickets redirect assigned is enabled? I’ll look at the issue itself tomorrow.
Yes, we can look at adding this, but the plugin needs unit tests before we do this so it’s not going to happen for at least a few months. The most important thing to address in this plugin is hardening the existing functionality so it’s easier to address compatibility issues (like the recent tag issue) when they arise.
Are you a developer? I’d be happy to help you get started with Discourse development so you can take over the plugin. Start out here and once you’re done I’ll set you up with the some beginner tasks involving the Tickets Plugin.
I completely understand, now that you explain the underlying issues with the plugin that need to be addressed before moving forward.
I’m a pretty novice “developer”, mostly focusing on WordPress (php, mysql, a bit of js), so a few months ago I would have loved to be mentored on how to get this functionality integrated into the plugin. But unfortunately I really don’t have time to spare now. My interest in Discourse is just for the new forums that I created/migrated for the open-source CyberPanel web control panel.
The developer doesn’t have time or skill/inclination for community management, so he is largely left flying solo. Things have improved a lot since I intervened 6 months ago and moved everything - support, docs etc… - to Discourse. The final piece of the puzzle is to have some sort of tickets management system to better allow the community and developer to track what needs to be done.