396170b438
Ships the design spec at docs/superpowers/specs/2026-05-27-owner-approval-flow-design.md. What's new on central (fusion_helpdesk_central 19.0.1.2.0 -> 19.0.2.0.0): - Engagement model: 8 new fields on helpdesk.ticket (state, snapshotted owner email/name, single-use UUID4 token, sent/reminded/decided timestamps, AI summary, stored-computed turnaround hours). - Wizard: single + bulk modes on one fusion.helpdesk.engagement.wizard TransientModel with a child wizard.line for per-ticket bulk summaries. default_get pulls the OpenAI summary on open; AI fan-out for bulk is parallel via ThreadPoolExecutor (max 5 workers, 30s overall cap). - OpenAI client in utils.py — stdlib urllib, 15s per-call timeout, every failure collapses to '' so the wizard's manual-summary fallback fires. - Public portal: /fusion_helpdesk/engagement/<token>/<decision> GET + POST, four branded standalone QWeb pages (confirm/done/invalid/error). Token is single-use, cleared on confirm. Decision posts a public comment attributed to the resolved owner partner; chatter propagates to the employee's My Tickets thread per the "fully visible" UX choice. - Mail templates (single + bulk) with magic-link buttons. Bulk template renders one card per ticket, each with its own approve/reject URL. - Reminder cron: daily, single-shot per engagement, configurable via fusion_helpdesk_central.engagement_reminder_days ICP (default 3, 0 disables). - Reporting dashboard: pivot/graph/list/kanban over helpdesk.ticket filtered to engaged ones, with avg-turnaround measure. Menu lives under Helpdesk > Reporting > Owner Engagements. - Client_key extended with owner_email/owner_name fields; ticket.create upserts them from the client-side piggyback (no new sync endpoint). - 100% coverage on utils + integration tests on wizard, controllers, re-engagement, cron, computed turnaround. OpenAI mocked in CI. What's new on client (fusion_helpdesk 19.0.1.7.1 -> 19.0.2.0.0): - Two new ICP settings: fusion_helpdesk.owner_email / .owner_name with a new "Owner Approval" block in Settings > Fusion Helpdesk. - controllers/main.py::submit piggybacks both keys on every ticket payload so central keeps client_key.owner_email/name fresh automatically. Verified live end-to-end on entech -> nexa: payload upsert, wizard with mocked AI, action_send, portal GET/POST/GET-again cycle, second click hits the friendly invalid-token page. Token entropy = 122 bits (UUID4).
72 lines
3.1 KiB
Python
72 lines
3.1 KiB
Python
# -*- coding: utf-8 -*-
|
|
# Copyright 2026 Nexa Systems Inc.
|
|
# License OPL-1
|
|
"""Configuration for the Fusion Helpdesk Reporter.
|
|
|
|
Stores the central Odoo Helpdesk endpoint that submissions are
|
|
forwarded to. Defaults point at erp.nexasystems.ca / nexamain;
|
|
each client deployment can override per system parameter.
|
|
"""
|
|
from odoo import api, fields, models
|
|
|
|
|
|
class ResConfigSettings(models.TransientModel):
|
|
_inherit = 'res.config.settings'
|
|
|
|
fhd_remote_url = fields.Char(
|
|
string='Helpdesk Remote URL',
|
|
config_parameter='fusion_helpdesk.remote_url',
|
|
help='Base URL of the central Odoo running the Helpdesk app, '
|
|
'e.g. https://erp.nexasystems.ca',
|
|
)
|
|
fhd_remote_db = fields.Char(
|
|
string='Helpdesk Remote DB',
|
|
config_parameter='fusion_helpdesk.remote_db',
|
|
help='Database name on the remote Odoo (e.g. nexamain).',
|
|
)
|
|
fhd_remote_login = fields.Char(
|
|
string='Helpdesk Remote Login',
|
|
config_parameter='fusion_helpdesk.remote_login',
|
|
help='Service-account login on the remote Odoo. Needs create '
|
|
'rights on helpdesk.ticket and ir.attachment.',
|
|
)
|
|
fhd_remote_password = fields.Char(
|
|
string='Helpdesk Remote Password / API Key',
|
|
config_parameter='fusion_helpdesk.remote_password',
|
|
help='Service-account password or API key. Stored in '
|
|
'ir.config_parameter — restrict read access if needed.',
|
|
)
|
|
fhd_remote_team_id = fields.Integer(
|
|
string='Helpdesk Team ID',
|
|
config_parameter='fusion_helpdesk.remote_team_id',
|
|
help='Optional. ID of the helpdesk.team on the remote that '
|
|
'should own all incoming tickets. Leave blank to use '
|
|
'the remote default routing.',
|
|
)
|
|
fhd_client_label = fields.Char(
|
|
string='Client Label (auto-prepended to subject)',
|
|
config_parameter='fusion_helpdesk.client_label',
|
|
help='Short tag prefixed onto the ticket subject so support '
|
|
'can tell which client deployment a ticket came from. '
|
|
'e.g. "ENTECH" → "[ENTECH] My subject"',
|
|
)
|
|
# Owner contact for the central engagement / approval flow. Optional —
|
|
# leaving these blank disables the "Request Owner Approval" button on
|
|
# the central side for this client. Both values piggyback on every
|
|
# ticket submission (see controllers/main.py::submit) so central always
|
|
# has the latest contact without a dedicated sync endpoint.
|
|
fhd_owner_email = fields.Char(
|
|
string='Owner Email',
|
|
config_parameter='fusion_helpdesk.owner_email',
|
|
help='Email of the real decision-maker at your company — the '
|
|
'person who can approve feature requests or bug-fix scope. '
|
|
'Used when central support hits a ticket that needs sign-off. '
|
|
'Leave blank if your deployment doesn\'t require approvals.',
|
|
)
|
|
fhd_owner_name = fields.Char(
|
|
string='Owner Name',
|
|
config_parameter='fusion_helpdesk.owner_name',
|
|
help='Display name for the owner — shown in the approval email '
|
|
'greeting and in the chatter attribution after they decide.',
|
|
)
|