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
@xrachelthegreatx
Make a ticket.
Suggestion! Maybe make it possible for claimed/closed tickets viewable in a list? For example, /ticket view claimed or /ticket view closed, because I don't want a forgetful mod to claim a ticket and then never close it. Unless this is already do-able and I just haven't seen it? Either way, love the plugin
This plugin is actually useless since you can't reply to the tickets at all.
If your plugin works with other versions than 1.8.1, you must list all of the supported versions or version ranges in a file's supported versions.
I've fixed the permission issue. Just got to wait for the Bukkit staff to accept the file and then you guys can use it.
Hi, im having that error too while using PEX. Would be epic if you could fix it as soon as possible, it is a great and simple plugin :)
Hi, I added a suggestion as a ticket: http://dev.bukkit.org/bukkit-plugins/simple-ticket-manager/tickets/1-ticket-comments/
@GodsMustache
That is a database error. It seems the plugin didn't send any queries to the database for 8 hours then when it went to send a query the connection was closed. It should automatically reopen the connection when the query was sent. I don't know why it didn't.
I will have a look at that tonight if I get chance.
There are issues with the permissions. Seems to be very select on who it doesn't work for though.
I'm getting some people to try it out for me. If they say the fix has worked then I will upload the file to Bukkit when I get home from work tonight.
@Thepom360
This server is running CraftBukkit version git-Spigot-eb39b47-0899683 (MC: 1.8) (Implementing API version 1.8-R0.1-SNAPSHOT)
http://pastebin.com/QzWrNCnb
There is that error which I think is something entirely different though.
@GodsMustache
What Build of Bukkit are you using? any Console errors?
@Thepom360
Yeah it should and I don't know why is doesn't. I usually edit the permissions.yml to add new nodes and such but I have tried it by issuing commands too and it doesn't seem to work.
@GodsMustache
Using Pex? remove the old ticket.use... /pex group <group name> add ticket.use then /pex reload.
and should work.
I can't get the permission node to work for ticket.use. Works when I am opped but not when I designate the permission node to the group I am in.
http://i.imgur.com/lgykyxt.png
@Jwoolley
Any way you can pull username also on the ticket system so there is a separate column giving the actual username so i can track them via DB instead of trying to track the UUID and finding out who.
@GodsMustache
Fixing that issue right now. Will be a update soon to handle errors better.
@Thepom360
I will see if I can possible do that this weekend.
@LegendaryKoala
I will need more information than that, any errors? How many are missing?
I have only tested it against Minecraft vanilla 1.8. So I have no idea how it reacts to moded versions. No reason it shouldn't work.
Ticket View is not appropriately showing all open tickets. This is on a cauldron 1.7.10 server.
@Jwoolley
Maybe add on the status time last ticket was Open ( in hours) and Maybe a reply command?
as for the info command.... allow up to 20 tickets in config? so the command would become /ticket info page 1,2,3,4 or make it so when /ticket info is enter it say Please select your Ticket number... and add config option to update player that the ticket closed by [admin name]
it's up to you.
When issuing /ticket claim
http://pastebin.com/QFYzDFcw
EDIT: found my problem and yes it was operator error lol