Tickets 插件 🎟

[IreneT (Irene Tolentino)]

这是最新错误的详细信息 @RGJ 谢谢`

`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...</p>", 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]

问题：有人目前在使用这个支持/工单插件吗：

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…

如果在使用，它是否正常工作并且已更新？或者，如果您有其他选项，我很乐意了解一下。

[JonM (Jon)]

+1，我也想知道！

[letitia_jones]

这是否也会在 Github 中创建一个工单？

[merefield (Robert)]

不。

总的来说，我认为这个插件非常需要一些重要的企业/公司赞助来添加一些急需的功能（例如，允许任意组访问工单仪表板，而不仅仅是管理员等）。

[Livvux (Lucas)]

您好，
这个还管用吗？
我无法创建工单。

[reswild]

[quote=“Nick_Chomey, post:176, topic:97914”]
我稍微看了一下代码，注意到有几个地方写着诸如 currentUser.staff、is_staff 等等……所以我猜想，要么\n\n1. 放宽/移除这个规定，\n2. 添加另一个用户组（例如 TicketsTeam），我们可以自己创建和定义，或者\n3. 在 Tickets 设置中添加某种自定义机制，允许我们定义哪些组可以访问 Tickets。\n[/quote]\n\n我做了一些测试，放宽了规则，只要用户可以编辑主题，任何人都可以创建和编辑工单，这似乎按预期工作。我对 Ruby 的经验很少，所以我觉得自己没有资格正确实现和测试这一点，但这是我在我的开发站点上尝试的更改：Allow non-staff to add and edit tickets · reswild/discourse-tickets@8c3d0d5 · GitHub

[hellekin]

这是个 Bug @angus，当你点击 “ Ticket” 按钮时：

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)]

感谢 @hellekin 的报告。不幸的是，这个插件在我的优先级列表中排得很靠后，而且由于我确实没有精力，短期内不太可能得到任何关注。我现在将把它标记为 #broken。

[RGJ (Richard - Communiteq)]

Discourse 3.3 的大多数问题，包括 DButton 问题，现已得到解决。

[JayEnjoy (JeyChen)]

大家好，

Discourse 3.4.0 插件出现了一些错误：

1. 新主题表单上没有工单图标。
2. 工单仪表板界面混乱。

有什么解决办法吗？

[blazyrawr (Blazy)]

我也遇到了问题，在主题的工单创建中没有任何选项。

[hellekin]

对于 Priority、Status 和 Reason，您应该访问 /tag_groups 并将标签添加到 tickets_* 组。例如：

| 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]

但我认为这个话题应该像@angus去年建议的那样被标记为#broken，因为它显示了一个弃用警告，并且有一些未解决的bug，没有人会很快处理。

@merefield建议看看https://meta.discourse.org/t/discourse-workflow/347110。

[spj]

我确认我在安装了 Tickets 插件的 v0.2 (492353a20b1bc2bbcf739f1c88aaa46771e83561) 后的 Discourse 3.5.2 中看到了与 @JayEnjoy 和 @blazyrawr 相同的问​​题。听起来这个问题不会得到解决。除了已经提到的实验性工作流程插件之外，还有其他可行的替代品吗？