Plugin التذاكر 🎟

[IreneT (Irene Tolentino)]

Here are the details of the latest error @RGJ Thanks`

`Message (9 copies reported)

NoMethodError (undefined method `username' for #<Group id: 44, name: "Coaches", created_at: "2023-04-27 17:04:39.620341000 +0000", updated_at: "2023-04-27 17:04:39.620341000 +0000", automatic: false, user_count: 2, automatic_membership_email_domains: "", primary_group: false, title: nil, grant_trust_level: 1, incoming_email: nil, has_messages: false, flair_bg_color: "", flair_color: "", bio_raw: "All coaches who provide member coaching support in...", bio_cooked: "<p>All coaches who provide member coaching support...", allow_membership_requests: false, full_name: "Coaches", default_notification_level: 3, visibility_level: 0, public_exit: false, public_admission: false, membership_request_template: nil, messageable_level: 99, mentionable_level: 99, smtp_server: nil, smtp_port: nil, smtp_ssl: nil, imap_server: nil, imap_port: nil, imap_ssl: nil, imap_mailbox_name: "", imap_uid_validity: 0, imap_last_uid: 0, email_username: nil, email_password: nil, publish_read_state: false, members_visibility_level: 0, imap_last_error: nil, imap_old_emails: nil, imap_new_emails: nil, flair_icon: "", flair_upload_id: nil, allow_unknown_sender_topic_replies: false, smtp_enabled: false, smtp_updated_at: nil, smtp_updated_by_id: nil, imap_enabled: false, imap_updated_at: nil, imap_updated_by_id: nil, email_from_alias: nil, assignable_level: 99>)
(eval):4:in `_fast_attributes'
(eval):9:in `_fast_attributes'
app/controllers/application_controller.rb:549:in `render_json_dump'
app/controllers/application_controller.rb:418:in `block in with_resolved_locale'
app/controllers/application_controller.rb:418:in `with_resolved_locale'
lib/middleware/omniauth_bypass_middleware.rb:74:in `call'
lib/content_security_policy/middleware.rb:12:in `call'
lib/middleware/anonymous_cache.rb:369:in `call'
config/initializers/100-quiet_logger.rb:20:in `call'
config/initializers/100-silence_logger.rb:29:in `call'
lib/middleware/enforce_hostname.rb:24:in `call'
lib/middleware/request_tracker.rb:228:in `call'

Backtrace

activemodel (7.0.4.3) lib/active_model/attribute_methods.rb:458:in `method_missing'
active_model_serializers (0.8.4) lib/active_model/serializer.rb:99:in `block in attribute'
(eval):4:in `_fast_attributes'
active_model_serializers (0.8.4) lib/active_model/serializer.rb:468:in `rescue in attributes'
active_model_serializers (0.8.4) lib/active_model/serializer.rb:455:in `attributes'
active_model_serializers (0.8.4) lib/active_model/serializer.rb:480:in `_serializable_hash'
active_model_serializers (0.8.4) lib/active_model/serializer.rb:359:in `serializable_hash'
active_model_serializers (0.8.4) lib/active_model/serializer.rb:343:in `as_json'
plugins/discourse-tickets/serializers/tickets/ticket_serializer.rb:29:in `assigned'
(eval):9:in `_fast_attributes'

Env

HTTP HOSTS: sandy.albacore.co`

[discoursejl]

Question: Is anyone currently using this support/ticket plugin:

Tickets Plugin

Repo Summary This plugin adds a ticketing system to Discourse. It requires tagging to be enabled and works best alongside the Assign Plugin. It is based on @tobiaseigen’s original spec, and has been built in collaboration with @tobiaseigen and an awesome Ruby for Good team, for the benefit of both Namati and the Discourse community. Notes When you install the plugin, three new tag groups are added tickets_priority, tickets_reason and tickets_status. Add tags to these groups (at /tag_group…

If so, is it working and updated? Or if there are any other options I’d love to check them out.

[JonM (Jon)]

+1 for me! I’d like to know also!

[letitia_jones]

Does this create a ticket in Github as well?

[merefield (Robert)]

No.

In general I’d say this plugin is crying out for some significant enterprise/corporate sponsorship to add some much needed features (e.g. ticket dashboard exposed to arbitrary groups, not just sat in admin, etc.).

[Livvux (Lucas)]

Hi,
does this still work?
I cant manage to create tickets.

[reswild]

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

I did some testing with relaxing the rules so anyone can create and edit tickets as long as they can edit topics, and this seemed to work as intended. I have very little experience with Ruby so I don’t feel qualified to implement and test this properly, but here are the changes I tried on my dev site: Allow non-staff to add and edit tickets · reswild/discourse-tickets@8c3d0d5 · GitHub

[hellekin]

Here’s a bug @angus, when hitting the Ticket button:

Deprecation notice: DButton no longer supports @action as a string. Please refactor to use an closure action instead. [deprecation id: discourse.d-button-action-string] deprecated.js:55
Uncaught (in promise) TypeError: e.target is undefined
    assign task-actions.js:88
    assign tickets-controls.js:115
    Ember 2
    _triggerAction d-button.js:105
    click d-button.js:84
task-actions.js:88

[angus (Angus McLeod)]

Thanks for the report @hellekin. Unfortunately, this plugin is a ways down my priority list and it’s unlikely to receive any love in the near term as I don’t really have the bandwidth. I’m going to mark it as broken for now.

[RGJ (Richard - Communiteq)]

Most problems with Discourse 3.3, including the DButton one, have been resolved now.

[JayEnjoy (JeyChen)]

Hi team，

Here come some bugs from the plugin in Discourse 3.4.0

1. No tickets icon on new topics form appears.
2. The Tickets dashboard interface confused.

Any way to resolve this?

[blazyrawr (Blazy)]

Im having issues too, Its not showing any options inside of the ticket creation thing in the topics

[hellekin]

For Priority, Status and Reason, you should visit /tag_groups and add tags to the tickets_* groups. For example:

group	tags
tickets_priority	low, medium, high, critical
tickets_status	new, in-progress, on-hold, resolved, closed, wont-fix
tickets_reason	proj1, proj2, proj3, question, feedback, maintenance

[hellekin]

But I guess this topic should be marked as broken as @angus suggested last year since it shows a deprecation warning and has some outstanding bugs that nobody is going to attend soon.

@merefield suggested looking into Discourse Workflow instead.