d7ec91b0f1
Three coordinated changes on top of the section grouping: 1. **Mark as Critical** — a red chip on the New tab sets priority='3' when submitted. The central post-create hook auto-applies a "Critical" helpdesk.tag (shipped via fusion_helpdesk_central data XML, noupdate=1 so support can recolor without losing it on upgrade), giving support a kanban-groupable signal that doesn't rely on remembering what priority='3' means. Scoped to in-app-channel tickets only, so a support agent manually setting Urgent on their own ticket isn't silently tagged. 2. **KPI cards above the sections** — Total / Open / Closed / Critical in a 4-up grid (auto-collapses to 2x2 under 540px). Each card uses its own saturated gradient so it reads on both light and dark mode — the dialog backdrop is irrelevant because the gradient brings its own background. Counts are computed in JS from state.tickets so they always match what's rendered below. 3. **Colored stage pills** — red Critical, green Solved, dark-yellow New, orange Cancelled, blue for In Progress / Testing / On Hold. Critical priority gets a *separate* red pill alongside the stage pill so you keep stage info even on escalated tickets. Stage matching is substring-based (lowercased) so a renamed "Resolved" or "Done" stage on central still maps to the green pill. Tests cover the new is_critical=True → priority='3' wiring and the default omission so SLA / stage defaults keep working for normal tickets. Bumps fusion_helpdesk to 19.0.1.7.0 and fusion_helpdesk_central to 19.0.1.2.0. End-to-end smoke test verified live: priority=3 + x_fc_client_label triggers the Critical tag.
49 lines
1.8 KiB
Python
49 lines
1.8 KiB
Python
# -*- coding: utf-8 -*-
|
|
# Copyright 2026 Nexa Systems Inc.
|
|
# License OPL-1 (Odoo Proprietary License v1.0)
|
|
{
|
|
'name': 'Fusion Helpdesk Reporter',
|
|
'version': '19.0.1.7.0',
|
|
'category': 'Productivity',
|
|
'summary': 'One-click in-app bug reporting & feature requesting — '
|
|
'auto-creates a helpdesk.ticket on a central Odoo Helpdesk.',
|
|
'description': """
|
|
Fusion Helpdesk Reporter
|
|
========================
|
|
A standalone module that gives every backend user a quick "Report an
|
|
Issue / Request a Feature" button in the Odoo top systray.
|
|
|
|
Submissions are forwarded over JSON-RPC / XML-RPC to a central Odoo
|
|
instance (typically the support shop's main Odoo) and become
|
|
`helpdesk.ticket` records with screenshots, file attachments, and
|
|
diagnostic context (URL, user agent, current user/company, error
|
|
code) automatically captured.
|
|
|
|
Designed to ship alongside any other Fusion / Nexa Systems client
|
|
module bundle. No dependencies on the rest of Fusion Plating.
|
|
""",
|
|
'author': 'Nexa Systems Inc.',
|
|
'website': 'https://www.nexasystems.ca',
|
|
'license': 'OPL-1',
|
|
'depends': ['base', 'web', 'mail'],
|
|
'data': [
|
|
'security/fusion_helpdesk_groups.xml',
|
|
'security/ir.model.access.csv',
|
|
'data/ir_config_parameter_data.xml',
|
|
'views/res_config_settings_views.xml',
|
|
],
|
|
'assets': {
|
|
'web.assets_backend': [
|
|
'fusion_helpdesk/static/src/scss/fusion_helpdesk.scss',
|
|
'fusion_helpdesk/static/src/xml/fusion_helpdesk_systray.xml',
|
|
'fusion_helpdesk/static/src/xml/fusion_helpdesk_dialog.xml',
|
|
'fusion_helpdesk/static/src/js/fusion_helpdesk_systray.js',
|
|
'fusion_helpdesk/static/src/js/fusion_helpdesk_dialog.js',
|
|
],
|
|
},
|
|
'images': ['static/description/icon.png'],
|
|
'installable': True,
|
|
'auto_install': False,
|
|
'application': False,
|
|
}
|