8cc02759b8
Adds a one-click 'loop the owner into the chatter' shortcut on the
ticket form — separate from the engagement approval flow, just keeps
the owner in the loop on ongoing communication.
What's new on helpdesk.ticket:
- x_fc_owner_display (computed Char): 'Kris Pathinather <kris@…>',
read live from fusion.helpdesk.client.key so a change to the owner
contact reflects immediately on every existing ticket.
- x_fc_owner_email_resolved (computed Char): email-only slice, drives
view visibility (the field + button only render when an owner is
configured).
- x_fc_owner_is_follower (computed Boolean): True when a partner with
the owner email is in message_partner_ids. Swaps the button for a
green 'Following' badge when the owner is already on the thread.
- action_add_owner_as_follower(): find-or-create the owner partner by
email and message_subscribe. Idempotent — second call is a no-op,
no duplicate partner. Raises UserError with a clear message if no
owner is configured.
View extension on the helpdesk ticket form: injects right after the
existing partner_id ('Customer') field in the customer side group,
so it reads as 'Customer | Owner Contact [Add as Follower]' — same
row, no layout shift when the state flips to 'Following'.
Tests cover the compute display in three states (configured,
no-client-label, no-owner-on-key), the action's three paths
(create-and-subscribe, reuse-existing-partner, idempotent-when-
already-following), and the UserError when nothing is configured.
Smoke-tested live on nexa: ticket with x_fc_client_label='ENTECH'
displays 'Kris Pathinather <kris@enplating.ca>'; first click adds
res.partner #723 to followers and flips owner_is_follower to True;
second click is a no-op.
Bumps fusion_helpdesk_central to 19.0.2.1.0.
45 lines
1.6 KiB
Python
45 lines
1.6 KiB
Python
# -*- coding: utf-8 -*-
|
|
# Copyright 2026 Nexa Systems Inc.
|
|
# License OPL-1
|
|
{
|
|
'name': 'Fusion Helpdesk Central — Client API Keys',
|
|
'version': '19.0.2.1.0',
|
|
'category': 'Productivity',
|
|
'summary': 'Admin UI on the central Odoo for issuing per-client API '
|
|
'keys used by fusion_helpdesk client deployments.',
|
|
'description': """
|
|
Fusion Helpdesk Central
|
|
=======================
|
|
Companion to `fusion_helpdesk`. Install on the central Odoo (the one
|
|
running the Helpdesk app) to manage **per-client API keys** instead of
|
|
shipping a shared bot password to every client deployment.
|
|
|
|
Each row in *Helpdesk → Configuration → Client API Keys* maps a client
|
|
label (e.g. ENTECH, MOBILITY) to a real `res.users.apikeys` row on the
|
|
shared bot user. The plaintext key is shown ONCE on creation; revoke
|
|
in one click if a deployment is compromised.
|
|
|
|
Depends only on `helpdesk`. No client-side install needed.
|
|
""",
|
|
'author': 'Nexa Systems Inc.',
|
|
'website': 'https://www.nexasystems.ca',
|
|
'license': 'OPL-1',
|
|
'depends': ['helpdesk'],
|
|
'data': [
|
|
'security/ir.model.access.csv',
|
|
'data/ir_config_parameter_data.xml',
|
|
'data/mail_template_ack.xml',
|
|
'data/mail_template_engagement.xml',
|
|
'data/helpdesk_tag_critical.xml',
|
|
'data/ir_cron_engagement_reminder.xml',
|
|
'views/fusion_helpdesk_client_key_views.xml',
|
|
'views/helpdesk_ticket_views.xml',
|
|
'views/engagement_wizard_views.xml',
|
|
'views/engagement_reporting_views.xml',
|
|
'views/portal_templates.xml',
|
|
],
|
|
'installable': True,
|
|
'auto_install': False,
|
|
'application': False,
|
|
}
|