# Tickets Plugin 🎟 **URL:** https://meta.discourse.org/t/tickets-plugin/97914 **Category:** Plugin **Tags:** pavilion **Created:** [September 24, 2018, 7:57am UTC](https://meta.discourse.org/t/tickets-plugin/97914 "2018-09-24T07:57:31Z") **Posts on this page:** 1 **Showing post:** 181
### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus) #### Post date: [May 9, 2022, 2:58pm UTC](https://meta.discourse.org/t/tickets-plugin/97914/181 "2022-05-09T14:58:50Z")
> [@Nick\_Chomey](#): > > 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` . 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. > [@Nick\_Chomey](#): > > 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 > > 1. relax/remove that stipulation, > 2. add another userGroup (e.g. TicketsTeam) that we could create and define ourselves, or > 3. add some sort of customization mechanism in the Tickets settings that allows us to define which groups have access to Tickets. 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. The main reason this plugin hasn’t gotten more attention is because we simply don’t have enough time. But there is a way you can help us solve that. Find a developer who has some experience with Ruby on Rails and JavaScript, or is willing to learn, put them in contact with me and I’ll mentor them as the maintainer of this plugin. I’m always willing to teach a man (or woman) to fish as the saying goes. > [@Nick\_Chomey](#): > > 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 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. > [@Learn how to start building stuff for Discourse if you're newbie (like myself)](https://meta.discourse.org/t/how-to-start-building-stuff-for-discourse-if-youre-newbie-like-myself/45954): > > There are a few ‘how to start’ guides for working with Discourse already and a wealth of useful info on meta, but I thought it might help to give an insight to the mental processes of starting from little, if any, prior coding experience to building substantial Discourse plugins. Discourse is written by experienced developers and has a large codebase. This can feel intimidating. This intimidation factor can be a significant barrier for novice developers. This is a kind of ‘psychological primer’… > [@Learn how to build Discourse plugins by helping me](https://meta.discourse.org/t/learn-how-to-build-discourse-plugins-by-helping-me/87048): > > If anyone wants to learn more about building Discourse plugins or just about Ruby on Rails and Ember.js, here’s a standing offer. I can train you, providing detailed personal direction on how to code; how Discourse works; how to think about your users; and how to think about product design in exchange for you working on tasks on the current task list for any of [my plugins](https://meta.discourse.org/u/angus/activity/topics). Why pay $5k for a General Assembly course when you can get personal coaching for free, and get the chance to work on co… --- _[View the full topic](https://meta.discourse.org/t/tickets-plugin/97914)._