Simple Ticket Manager
Overview
Find it hard to handle problems on your server? Well with Simple Ticket Manager players can create a report, which will then be reported to all the admins that have the ticket.use node, informing them that there is a new ticket open and that it needs assigning to someone to deal with.
Very simple to use and get problems sorted on your server sorted quickly.
You can also view information about who dealt with the ticket and when the problem was sorted. To see how admins are dealing with reports and how long they stay open for.
Features
- UUID Support
- SQLite and MySQL support
- Multiple World support
- Inform admins on join if there's any open tickets
- Detailed information about each report
- Works with Minecraft 1.8 and 1.7.10 (Does not support 1.7.9 or below)
Install
- Download the latest version of the plugin
- Drop the plugin your plugins folder
- Restart the server
- Edit your config.yml to the settings you wish to have
Permissions and Commands
report.use - Permission node to be able to create new reports. Default to everyone
ticket.view - Permission node to view status of each ticket. Inherits all below. Each default to op
ticket.view.open
ticket.view.assigned
ticket.view.assigned.all
ticket.view.closed
ticket.view.closed.all
ticket.info - Permission node to view ticket info. Default op
ticket.admin - Permission node to claim, close and unclaim tickets. Default op
ticket.teleport - Permission node to teleport to tickets. Default op
ticket.stats - Permission node to view stats about all tickets. Default op
ticket.reload - Permission node to reload the plugin. Default op
ticket.comments - Permission node to add comments to tickets. Default everyone
Report commands:
/report - Help on how to create new reports.
/report <reason> <description> - Reason must be 1 word, the rest of the command will be the description. For example: /report Grief Someone griefed my house!
Ticket commands:
/ticket - Help on how to do Ticket Commands.
/ticket view open - View what current tickets are open.
/ticket view assigned - View what current tickets are assigned to you.
/ticket view assigned all - View what current tickets are assigned to people.
/ticket view closed - View what tickets you have closed.
/ticket view closed all - View what tickets have been closed and by who.
/ticket info <ticket id> - View information about the ticket.
/ticket claim <ticket id> - Claim a ticket for yourself.
/ticket unclaim <ticket id> - Unclaim a ticket that you own.
/ticket close <ticket id> - Close a ticket once a report has been dealt with.
/ticket teleport <ticket id> - Teleport to where the report was located.
/ticket stats - View how many reports are open, assigned or closed
/ticket comment add <ticket id> <comment> - Add a comment to a ticket
/ticket comment view <ticket id> - View comments for a ticket
/ticket reload - Reload the plugin to get changes for either config.yml or messages.yml
Config
For help on setting up your config.yml click the link below
Coming soon
Videos
Thanks to JaxBillz for the video
Images
Creating the report:
Real time admin update:
Information about the ticket:
Claiming the ticket:
Closing the ticket:
Ticket stats:
Ticket notifications on Admin join:
To do
- Better multiple server support
- Configurable messages
I'm open to any suggestions anybody has.
Versions
v1.1.0
- Fix bug with ' causing SQL errors
- Added messages.yml
- Added config option to update all staff that a ticket has been closed
v1.0.0
- Initial relase
I am having alot of issues with the permissions not working please help.
i just tested it on my server and the user saying they dont get a message when a comment is added to ticket or when it get closed. u should add that a user get informed when his ticket get commented or closed. u also should add that he see when a staff claim it with a message like : " [staff] is now working on you Ticket [id] "
Great plugin !
I will create a web interface for a beter use ;)
When is finish, i contact you ;)
Could you add configurable messages please ?
I have this problem:
[11:35:08 WARN]: Exception in thread "Craft Scheduler Thread - 1140"
[11:35:08 WARN]: org.apache.commons.lang.UnhandledException: Plugin RewardVoting v6.0.3 generated an exception while executing task 41 at org.bukkit.craftbukkit.v1_9_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:56) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NoSuchMethodError: org.bukkit.Server.getOnlinePlayers()[Lorg/bukkit/entity/Player; at votepackage.Metrics.postPlugin(Metrics.java:336) at votepackage.Metrics.access$4(Metrics.java:328) at votepackage.Metrics$1.run(Metrics.java:223) at org.bukkit.craftbukkit.v1_9_R1.scheduler.CraftTask.run(CraftTask.java:71) at org.bukkit.craftbukkit.v1_9_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:53) ... 3 more
[11:35:08 WARN]: Exception in thread "Craft Scheduler Thread - 1143"
[11:35:08 WARN]: org.apache.commons.lang.UnhandledException: Plugin SimpleTicketManager v2.0.3 generated an exception while executing task 29 at org.bukkit.craftbukkit.v1_9_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:56) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NoSuchMethodError: org.bukkit.Server.getOnlinePlayers()[Lorg/bukkit/entity/Player; at uk.co.joshuawoolley.simpleticketmanager.Metrics.postPlugin(Metrics.java:335) at uk.co.joshuawoolley.simpleticketmanager.Metrics.access$400(Metrics.java:57) at uk.co.joshuawoolley.simpleticketmanager.Metrics$1.run(Metrics.java:223) at org.bukkit.craftbukkit.v1_9_R1.scheduler.CraftTask.run(CraftTask.java:71) at org.bukkit.craftbukkit.v1_9_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:53) ... 3 more
Hey, Neo here
I'm testing this plugin out, so far the database is sketchy but if I don't use SQL everything works as advertised!
A few suggestions if you wanted some: - Add a way to blacklist players/UUIDs from being able to report tickets (for those that abuse the system)
- On a similar strand, add a way to configure a max amount of reports per player/UUID
- Using an idea from an old plugin admin360, add a way to keep track of how many cases are successfully closed by a player/UUID
Thanks for the great plugin and good luck in the future!
Regards, Neo
Permission nodes don't work. I opened the plugin in JDgui to check if it was an issue with incorrect permissions (i.e., "tickets" instead of "ticket") as I've run into that issue before. Permissions are listed correctly, but still get that "I'm sorry, but you do not have permission to perform this command. Please contact the server administrators if you blieve that this is in error." message.
It only seems to work when I'm op. I also gave myself the permission ticket.* and same thing.
Using GroupManager and this is the only plugin I'm having issues with in regards to permissions.
@Joshii2201
Make sure you give yourself the correct permissions. - ticket.* will give you perms to everything or there is a list of permissions above if you want only wanting someone to have limited permissions.
Also its /ticket comment add (ticket number) (comment) and /ticket comment view (ticket number)
Everything works as I use the plugin daily.
Permissions don't work with the Plugin... No error in console but a messanging, that i don't have permission,
But /ticket comment isn't work. No errormessaging, nothing happen
Couple suggestions.
http://i.imgur.com/GfQNn1v.png
Display the comments when issuing /ticket info instead of having to use /ticket comment view. It will get rid of having to do an extra step/command
Also is it possible for the person who used /report to be notified when the ticket is resolved/see the comments I left them on the ticket. Something like "Your report has been closed. Type /randomcommand to see the comments/info/report" (or whatever you want to call it)
@egamadMC
Check your config.yml You can either turn off logging to console or change the timeframe in which it logs. I changed mine to once an hour.
How do I get rid of this console message:
[SimpleTicketManager] Database connection has been kept alive
It's spamming me every 10 minutes and makes the console hard to read.
@Filmjolk
@Jwoolley
I have the same issue, except it says that it is already closed.
edit: quick fix, The issue was that I never assigned it :P
@egamadMC
No one has reported that problem so I think there must be a issue with your permission system.
@Filmjolk
No one has reported the issue, you sure you are running latest version? You sure there's no console errors?
can't close tickets :/ trying as OP doesn't output any message in chat not console, just ignores the command.
Hello, I have a problem with your plugin. My mods can't access any commands (not even /ticket), even when they have the appropriate permissions.
I'm using PEX and I triple checked the permissions. I added them verbatim as you list them here, namely:
- ticket.view - ticket.teleport - ticket.admin - ticket.info - ticket.stats
@Corndogozy
The person who claimed the ticket can just do /ticket unclaim <ticket id>
@chinafriend
Maybe in a later update. I know nothing about GUI's. So would take me a while to learn.
I hope add a GUI for this plugin instead of type commands.
um well i would want to have my mods and admins use this, but if it was something that requires someone banned, i dont let my mods ban, so is it possible to unclaim it?
It will be good that when a staff claims aticket a message come to the person who did the report a message like "MrPesee has claim yor ticket!" and on when the ticket has been closed