Sorry this is a bit confusing to you. Staff can create tickets by selecting the big TICKET button below the topic title. Then add ticket details and select the checkmark button to save. If you donāt see the TICKET button, then you likely donāt have the tickets plugin enabled correctly.
Great plugin. Unfortunately, ticket_priority, ticket_status and ticket_reason tags donāt show up when clicking on the drop down menu as you can see on the attachment. Any idea?
Also reported on Github repo.
Iāve had this problem in the past but the bug that caused it seemed to have been fixed for a while now. Did you create the necessary tags for these? Are you using the latest versions of everything?
1 Like
Cannot reproduce, yet. (Iām running a midday refresh of Discourse on dev, though it might be just a Prod thing which can happen.)
Are you getting any javascript errors in the console? Do you have any other plugins installed?
What branch of Discourse are you on? What version?
No javascript error in the console. Here is an excerp of the app.yml.
## Which Git revision should this container use? (default: tests-passed)
#version: tests-passed
- sudo -E -u discourse git clone https://github.com/discourse/docker_manager.git
- sudo -E -u discourse git clone https://github.com/paviliondev/discourse-events.git
- sudo -E -u discourse git clone https://github.com/paviliondev/discourse-locations.git
- sudo -E -u discourse git clone https://github.com/discourse/discourse-chat-integration.git
- sudo -E -u discourse git clone https://github.com/discourse/discourse-data-explorer.git
- sudo -E -u discourse git clone https://github.com/discourse/discourse-checklist.git
- sudo -E -u discourse git clone https://github.com/discourse/discourse-footnote.git
- sudo -E -u discourse git clone https://github.com/discourse/discourse-tooltips.git
- sudo -E -u discourse git clone https://github.com/discourse/discourse-assign
- sudo -E -u discourse git clone https://github.com/paviliondev/discourse-topic-previews.git
- sudo -E -u discourse git clone https://github.com/gdpelican/retort.git
- sudo -E -u discourse git clone https://github.com/paviliondev/discourse-custom-wizard.git
- sudo -E -u discourse git clone https://github.com/discourse/discourse-canned-replies.git
- sudo -E -u discourse git clone https://github.com/angusmcleod/discourse-tickets.gitthanks. odd. I fixed this issue recently, yet some time ago: Tickets Plugin š - #115 by merefield
tests-passed is good 
Silently failing is very annoying! 
Do me a favour and rebuild with https://github.com/paviliondev/discourse-tickets.git Iāve got a sneaky suspicion ā¦
Confirmed. @angus has not merged the PR fix I pushed weeks ago. Replace with the fork above (itās our org anyway) and you will be good to go. Paviliondev fork is ahead 
2 Likes
Thank you! Everything works fine now with Paviliondev repo. 
3 Likes
There is now a single up-to-date repo for this plugin at https://github.com/paviliondev/discourse-tickets
2 Likes
Thanks for the report.
Iāve deployed a fix. The old table header component seems to have been replaced:
https://github.com/paviliondev/discourse-tickets/commit/a5e79c7cf762c10573b0b47225b79837994e27c0
https://github.com/paviliondev/discourse-tickets/commit/a3e259f5c35ba5344cc501ab0293717c8435fe1f
Could someone please explain the ātickets include groupā setting? I donāt seem to be able to understand it.
Name of group to include on all private messages with tickets.
I can see this description in the UI, but I cannot understand it, thatās why Iām asking here.
when a ticket is opened, someone needs to be notified about the new ticket. The group that you add there, will get the notification.
When you edit the ticket details for a message, you will be able to see a field for users and groups to include in the message. This is a handy feature to make it easy to quickly add them as you add ticket tags for priority, status and reason. The group you put in this admin setting will be included by default. You can always add/remove users and groups from here when you edit ticket details.
This is especially handy because, using discourse as a ticket system, you want to make sure it is not just one person who is included for continuity and to ensure followup.
All of this said, I donāt use the tickets plugin anymore. There are so many core discourse features for making sure followup happens, including Improved Bookmarks with Reminders and Assigned topic summary for groups.
5 Likes
Can closing a ticket also close the topic? I have some topics with tickets and I wanted to close it. So I went to the edit topic and changed the status to closed.
The thing is that a closed ticket will almost always mean to close a topic. Itās almost like itās redundant for me to close twice. Rather, the close ticket is only adding a tag that says āclosedā.
Moreover, can we just order the topics based on ticket status? When we go to Settings->Appearance, we can sort Topic List by activity, which seems is the closest.
Is there any other way to distinguish tickets by color. In a site where you have multiple tickets for bug reporting, itās important to sort by ticket status.
2 Likes
Love that idea. At least as an option 
3 Likes
Thanks, but what about my second idea of ordering tickets by ticket status? The open tickets should be on the top.
1 Like
Also good. We should add this plugin to the Feature Requests wizard so you can add those. Iāll look at that in the morning.
2 Likes