# 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:** 20
**Page:** 7

<div class="post-metadata">

### Author: ![tobiaseigen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tobiaseigen/32/539204_2.png) [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)
#### Post date: [April 9, 2020, 10:03pm UTC](https://meta.discourse.org/t/tickets-plugin/97914/128 "2020-04-09T22:03:08Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![eax](https://avatars.discourse-cdn.com/v4/letter/e/7993a0/32.png) [@eax](https://meta.discourse.org/u/eax)
#### Post date: [April 24, 2020, 4:21pm UTC](https://meta.discourse.org/t/tickets-plugin/97914/129 "2020-04-24T16:21:55Z")

</div>

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?

 ![image](https://global.discourse-cdn.com/meta/original/3X/2/8/28540355c1debff574a7ce190003544461073338.png)

Also [reported](https://github.com/angusmcleod/discourse-tickets/issues/5) on Github repo.

---

<div class="post-metadata">

### Author: ![downey](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/downey/32/166878_2.png) [@downey](https://meta.discourse.org/u/downey)
#### Post date: [April 24, 2020, 9:03pm UTC](https://meta.discourse.org/t/tickets-plugin/97914/130 "2020-04-24T21:03:32Z")

</div>

> [@eax](#):
>
> Unfortunately, ticket\_priority, ticket\_status and ticket\_reason tags don’t show up when clicking on the drop down menu

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?

---

<div class="post-metadata">

### Author: ![eax](https://avatars.discourse-cdn.com/v4/letter/e/7993a0/32.png) [@eax](https://meta.discourse.org/u/eax)
#### Post date: [April 24, 2020, 9:07pm UTC](https://meta.discourse.org/t/tickets-plugin/97914/131 "2020-04-24T21:07:54Z")

</div>

Discourse was updated and the plugin installed yesterday.

 ![image](https://global.discourse-cdn.com/meta/original/3X/f/4/f44f9e338cf14574586f3ddfc7c36fa3a388d2a7.png)

 ![image](https://global.discourse-cdn.com/meta/original/3X/7/c/7c1a170c20abc0364362b27e4c65157c6bcc0917.png)

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [April 24, 2020, 9:50pm UTC](https://meta.discourse.org/t/tickets-plugin/97914/132 "2020-04-24T21:50:22Z")

</div>

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?

---

<div class="post-metadata">

### Author: ![eax](https://avatars.discourse-cdn.com/v4/letter/e/7993a0/32.png) [@eax](https://meta.discourse.org/u/eax)
#### Post date: [April 24, 2020, 10:00pm UTC](https://meta.discourse.org/t/tickets-plugin/97914/133 "2020-04-24T22:00:59Z")

</div>

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.git

```

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [April 24, 2020, 10:06pm UTC](https://meta.discourse.org/t/tickets-plugin/97914/134 "2020-04-24T22:06:58Z")

</div>

thanks. odd. I fixed this issue recently, yet some time ago: [Tickets Plugin 🎟 - #115 by merefield](https://meta.discourse.org/t/tickets-plugin/97914/115)

`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](https://github.com/angusmcleod/discourse-tickets/pull/6) 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 🚀 😉

---

<div class="post-metadata">

### Author: ![eax](https://avatars.discourse-cdn.com/v4/letter/e/7993a0/32.png) [@eax](https://meta.discourse.org/u/eax)
#### Post date: [April 24, 2020, 10:53pm UTC](https://meta.discourse.org/t/tickets-plugin/97914/135 "2020-04-24T22:53:19Z")

</div>

Thank _you_! Everything works fine now with Paviliondev repo. 🙇‍♂️

---

<div class="post-metadata">

### 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: [April 25, 2020, 1:43am UTC](https://meta.discourse.org/t/tickets-plugin/97914/136 "2020-04-25T01:43:41Z")

</div>

There is now a single up-to-date repo for this plugin at [GitHub - paviliondev/discourse-tickets: Ticketing system for Discourse · GitHub](https://github.com/paviliondev/discourse-tickets) 👍

---

<div class="post-metadata">

### Author: ![diabolino](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/diabolino/32/141385_2.png) [@diabolino](https://meta.discourse.org/u/diabolino)
#### Post date: [June 2, 2020, 4:23pm UTC](https://meta.discourse.org/t/tickets-plugin/97914/137 "2020-06-02T16:23:09Z")

</div>

plugin not working with 2.5.0.beta6

the dashboard is no longer displayed at all

 ![ticket](https://global.discourse-cdn.com/meta/original/3X/5/7/57fe3d65999c519ecb2167400d6ee3bbae28ef5b.png)

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [June 2, 2020, 6:04pm UTC](https://meta.discourse.org/t/tickets-plugin/97914/138 "2020-06-02T18:04:33Z")

</div>

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/a5e79c7cf762c10573b0b47225b79837994e27c0)

[https://github.com/paviliondev/discourse-tickets/commit/a3e259f5c35ba5344cc501ab0293717c8435fe1f](https://github.com/paviliondev/discourse-tickets/commit/a3e259f5c35ba5344cc501ab0293717c8435fe1f)

---

<div class="post-metadata">

### Author: ![meglio](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/meglio/32/71444_2.png) [@meglio](https://meta.discourse.org/u/meglio)
#### Post date: [August 10, 2020, 1:32am UTC](https://meta.discourse.org/t/tickets-plugin/97914/139 "2020-08-10T01:32:29Z")

</div>

Could someone please explain the “tickets include group” setting? I don’t seem to be able to understand it.

---

<div class="post-metadata">

### Author: ![IAmGav](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/iamgav/32/235598_2.png) [@IAmGav](https://meta.discourse.org/u/IAmGav)
#### Post date: [August 10, 2020, 10:37am UTC](https://meta.discourse.org/t/tickets-plugin/97914/140 "2020-08-10T10:37:39Z")

</div>

Name of group to include on all private messages with tickets.

 ![image](https://global.discourse-cdn.com/meta/original/3X/2/7/274a4cc9f0bdac17c548fddb388b631474149b98.png)

---

<div class="post-metadata">

### Author: ![meglio](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/meglio/32/71444_2.png) [@meglio](https://meta.discourse.org/u/meglio)
#### Post date: [August 10, 2020, 10:51am UTC](https://meta.discourse.org/t/tickets-plugin/97914/141 "2020-08-10T10:51:06Z")

</div>

I can see this description in the UI, but I cannot understand it, that’s why I’m asking here.

---

<div class="post-metadata">

### Author: ![IAmGav](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/iamgav/32/235598_2.png) [@IAmGav](https://meta.discourse.org/u/IAmGav)
#### Post date: [August 10, 2020, 10:54am UTC](https://meta.discourse.org/t/tickets-plugin/97914/142 "2020-08-10T10:54:55Z")

</div>

when a ticket is opened, someone needs to be notified about the new ticket. The group that you add there, will get the notification.

---

<div class="post-metadata">

### Author: ![tobiaseigen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tobiaseigen/32/539204_2.png) [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)
#### Post date: [August 10, 2020, 1:29pm UTC](https://meta.discourse.org/t/tickets-plugin/97914/143 "2020-08-10T13:29:57Z")

</div>

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](https://meta.discourse.org/t/improved-bookmarks-with-reminders/144542) and [Assigned topic summary for groups](https://meta.discourse.org/t/assigned-topic-summary-for-groups/159036).

---

<div class="post-metadata">

### Author: ![AntiMetaman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/antimetaman/32/186978_2.png) [@AntiMetaman](https://meta.discourse.org/u/AntiMetaman)
#### Post date: [August 17, 2020, 10:02pm UTC](https://meta.discourse.org/t/tickets-plugin/97914/144 "2020-08-17T22:02:45Z")

</div>

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.

 ![image](https://global.discourse-cdn.com/meta/original/3X/c/b/cb6506438f538ddd37e82d1f9b6ebc177615549a.png)

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.

![image](https://global.discourse-cdn.com/meta/original/3X/e/6/e6481bbc11a7589c9031cb9556829178ee57e64d.png)

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.

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [August 17, 2020, 10:19pm UTC](https://meta.discourse.org/t/tickets-plugin/97914/145 "2020-08-17T22:19:06Z")

</div>

> [@AntiMetaman](#):
>
> Can closing a ticket also close the topic?

Love that idea. At least as an option 👍🏻

---

<div class="post-metadata">

### Author: ![AntiMetaman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/antimetaman/32/186978_2.png) [@AntiMetaman](https://meta.discourse.org/u/AntiMetaman)
#### Post date: [August 17, 2020, 10:28pm UTC](https://meta.discourse.org/t/tickets-plugin/97914/146 "2020-08-17T22:28:08Z")

</div>

Thanks, but what about my second idea of ordering tickets by ticket status? The open tickets should be on the top.

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [August 17, 2020, 10:31pm UTC](https://meta.discourse.org/t/tickets-plugin/97914/147 "2020-08-17T22:31:27Z")

</div>

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.

[Previous page](https://meta.discourse.org/t/tickets-plugin/97914.md?page=6)

[Next page](https://meta.discourse.org/t/tickets-plugin/97914.md?page=8)
