11 Commits

Author SHA1 Message Date
Stéphan Sainléger
8aeb08ce14 [MIG] helpdesk_timesheet_exclude_from_sale_order: migrate to 18.0 2026-03-17 21:48:12 +01:00
Stéphan Sainléger
bf91f01387 [MIG] helpdesk_transfer_timesheet_to_task: migrate to 18.0 2026-03-17 21:45:49 +01:00
Stéphan Sainléger
48185f0124 [MIG] helpdesk_convert_ticket_to_task: migrate to 18.0 2026-03-17 21:41:37 +01:00
Stéphan Sainléger
baf64eac45 [MIG] helpdesk_user_default_ticket_team: migrate to 18.0 2026-03-17 21:31:15 +01:00
Stéphan Sainléger
5d152e096f [MIG] helpdesk_ticket_task_domain: migrate to 18.0 2026-03-17 21:23:49 +01:00
Stéphan Sainléger
3697b246f1 [MIG] helpdesk_portal_timesheet: migrate to 18.0 2026-03-17 21:23:49 +01:00
Stéphan Sainléger
b61f34f700 [NEW] helpdesk_portal_ticket_list_defaults: create add-on
this add-on comes from add-on helpdesk_portal_ticket_custom in v16.0
which has been refactorized.
2026-03-17 21:23:49 +01:00
Stéphan Sainléger
c8b37a22e5 [MIG] helpdesk_portal_ticket_priority_form: migrate to 18.0 2026-03-17 21:23:49 +01:00
Stéphan Sainléger
c067fcf28f [MIG] helpdesk_portal_ticket_enriched_description_form: migrate to 18.0 2026-03-17 21:23:49 +01:00
Stéphan Sainléger
a6943e96be [MIG] helpdesk_request_type: migrate to 18.0 2026-03-17 15:07:14 +01:00
Stéphan Sainléger
0720f67a14 [MIG] init 18.0 2026-01-16 16:25:10 +01:00
44 changed files with 640 additions and 334 deletions

View File

@@ -3,15 +3,46 @@ helpdesk_convert_ticket_to_task
===============================
This module aims to convert a ticket into a task.
For this, it adds a button in the ticket view "Convert to task".
It automatically fills up many fields (check the function button_convert_to_task for details)
It adds a "Convert to task" button in the ticket form view (in the button box).
When clicked, a confirmation dialog appears, then the conversion process:
* Creates a new task with the following fields copied from the ticket:
* Name
* Description
* Project
* Assigned user
* Partner
* Priority
* Matches the task's service and request type based on the ticket's category
and request type (by name matching).
* Copies all chatter messages and their attachments to the new task.
* Copies all attachments from the ticket to the task.
* Copies all followers (subscribers) to the new task.
* Posts a message in the new task's chatter with a link to the original ticket.
* Posts a message in the ticket's chatter with a link to the new task.
* Archives the ticket and links it to the new task.
* Transfers all timesheets from the ticket to the task.
* Redirects the user to the newly created task form.
# Installation
Use Odoo normal module installation procedure to install
`helpdesk_convert_ticket_to_task`.
This module depends on:
* `helpdesk_mgmt`: provides the base helpdesk ticket functionality.
* `helpdesk_mgmt_project`: provides the link between tickets and projects.
* `helpdesk_request_type`: provides the request type field on tickets.
* `project_request_data`: provides the service and request type fields on tasks.
* `project_task_add_very_high`: provides extended priority values (2 and 3) on
tasks to match ticket priorities.
* `helpdesk_transfer_timesheet_to_task`: provides the timesheet transfer
functionality from ticket to task.
# Known issues / Roadmap
A current limitation is that one task can be linked to many tickets.
@@ -20,7 +51,7 @@ but are not updated when the linked tickets are updated.
# Bug Tracker
Bugs are tracked on `our issues website <https://github.com/elabore-coop/helpdesk-tools/issues>`\_. In case of
Bugs are tracked on [our issues website](https://git.elabore.coop/Elabore/helpdesk-tools/issues). In case of
trouble, please check there if your issue has already been
reported. If you spotted it first, help us smashing it by providing a
detailed and welcomed feedback.

View File

@@ -2,7 +2,7 @@
# License AGPL-3.0 or later (http://www.gnu.org/licenses/agpl).
{
"name": "helpdesk_convert_ticket_to_task",
"version": "16.0.1.0.0",
"version": "18.0.1.0.0",
"author": "Elabore",
"website": "https://elabore.coop",
"maintainer": "Quentin Mondot",

View File

@@ -1,4 +1,7 @@
from odoo import _, models, api
from markupsafe import Markup
from odoo import _, api, models
class HelpdeskTicket(models.Model):
_inherit = "helpdesk.ticket"
@@ -7,42 +10,41 @@ class HelpdeskTicket(models.Model):
user_ids = [self.user_id.id]
task_service_id, request_type_id = self._match_task_service_and_request_type(
ticket_category_id=self.category_id.id,
ticket_request_type_id=self.request_type_id.id
ticket_request_type_id=self.request_type_id.id,
)
task = self.env["project.task"].create({
"name": self.name,
"description": self.description,
"project_id": self.project_id.id,
"user_ids": user_ids,
"partner_id": self.partner_id.id,
"service_id": task_service_id,
"request_type_id": request_type_id,
"priority": self.priority
})
task = self.env["project.task"].create(
{
"name": self.name,
"description": self.description,
"project_id": self.project_id.id,
"user_ids": user_ids,
"partner_id": self.partner_id.id,
"service_id": task_service_id,
"request_type_id": request_type_id,
"priority": self.priority,
}
)
# copy chatter
for msg in reversed(self.message_ids):
msg.copy({
'model': 'project.task',
'res_id': task.id
})
msg.copy({"model": "project.task", "res_id": task.id})
# copy attachments inserted in the messages
for attach in msg.attachment_ids:
attach.copy({
'res_model': 'project.task',
'res_id': task.id,
'res_name': task.name
})
attach.copy(
{
"res_model": "project.task",
"res_id": task.id,
"res_name": task.name,
}
)
# copy attachments not added in a message
for attachment in self.attachment_ids:
attachment.copy({
'res_model': 'project.task',
'res_id': task.id,
'res_name': task.name
})
attachment.copy(
{"res_model": "project.task", "res_id": task.id, "res_name": task.name}
)
# copy subscribers
task.message_subscribe(partner_ids=self.message_partner_ids.ids)
@@ -50,25 +52,26 @@ class HelpdeskTicket(models.Model):
# warn (in the chatter) that the task is a copy
base_url = self.env["ir.config_parameter"].sudo().get_param("web.base.url")
ticket_url = f"{base_url}/web#id={self.id}&model=helpdesk.ticket&view_type=form"
task_message = _(
"This task has been converted from a ticket. You can find the original ticket <a href='%(ticket_url)s' target='_blank'>on this link</a>.",
ticket_url=ticket_url
)
task_message = Markup(
_(
"This task has been converted from a ticket. You can find the "
"original ticket <a href='%(ticket_url)s' target='_blank'>on this link</a>."
)
) % {"ticket_url": ticket_url}
task.message_post(body=task_message)
# warn (in the chatter) that the ticket has been converted
task_url = f"{base_url}/web#id={task.id}&model=project.task&view_type=form"
ticket_message = _(
"This ticket has been converted into a task. You can find it <a href='%(task_url)s' target='_blank'>on this link</a>.",
task_url=task_url
)
ticket_message = Markup(
_(
"This ticket has been converted into a task. You can find it "
"<a href='%(task_url)s' target='_blank'>on this link</a>."
)
) % {"task_url": task_url}
self.message_post(body=ticket_message)
# archive the ticket
self.write({
"active": False,
"task_id": task.id
})
self.write({"active": False, "task_id": task.id})
# transfer timesheets from ticket to task
self._onchange_task_id()
@@ -81,23 +84,23 @@ class HelpdeskTicket(models.Model):
}
def _match_task_service_and_request_type(
self,
ticket_category_id: int,
ticket_request_type_id: int
self, ticket_category_id: int, ticket_request_type_id: int
) -> tuple[int, int]:
"""
This function permits to match the task service_id and request_type from the ticket category and request type
"""
helpdesk_ticket_category = self.env["helpdesk.ticket.category"].search(
[("id", "=", ticket_category_id)],
limit=1
[("id", "=", ticket_category_id)], limit=1
)
task_service = self.env["task.service"].search(
[("name", "=", helpdesk_ticket_category.name)]
)
task_service = self.env["task.service"].search([("name", "=", helpdesk_ticket_category.name)])
helpdesk_ticket_request_type = self.env["helpdesk.request.type"].search(
[("id", "=", ticket_request_type_id)],
limit=1
[("id", "=", ticket_request_type_id)], limit=1
)
task_request_type = self.env["request.type"].search(
[("name", "=", helpdesk_ticket_request_type.name)]
)
task_request_type = self.env["request.type"].search([("name", "=", helpdesk_ticket_request_type.name)])
return task_service.id, task_request_type.id

View File

@@ -1,37 +0,0 @@
====================================
helpdesk_portal_ticket_custom
====================================
Customization for ticket portal view.
# Installation
Use Odoo normal module installation procedure to install
`helpdesk_portal_ticket_custom`.
# Known issues / Roadmap
None yet.
# Bug Tracker
Bugs are tracked on `our issues website <https://github.com/elabore-coop/helpdesk-tools/issues>`\_. In case of
trouble, please check there if your issue has already been
reported. If you spotted it first, help us smashing it by providing a
detailed and welcomed feedback.
# Credits
## Contributors
- Joris Scampucci
## Funders
The development of this module has been financially supported by:
- Elabore (https://elabore.coop)
## Maintainer
This module is maintained by Elabore.

View File

@@ -1 +0,0 @@
from . import models

View File

@@ -1,35 +0,0 @@
# Copyright 2024 Joris Scampucci" (Elabore)
# License AGPL-3.0 or later (http://www.gnu.org/licenses/agpl).
{
"name": "helpdesk_portal_ticket_custom",
"version": "16.0.1.0.0",
"author": "Elabore",
"website": "https://elabore.coop",
"maintainer": "Joris Scampucci",
"license": "AGPL-3",
"category": "Tools",
"summary": "Customization for ticket portal view.",
# any module necessary for this one to work correctly
"depends": [
"base",
"helpdesk_mgmt",
],
"qweb": [],
"external_dependencies": {
"python": [],
},
# always loaded
"data": [
"views/portal_ticket_views.xml",
],
# only loaded in demonstration mode
"demo": [],
"js": [],
"css": [],
"installable": True,
# Install this module automatically if all dependency have been previously
# and independently installed. Used for synergetic or glue modules.
"auto_install": False,
"application": False,
}

View File

@@ -1 +0,0 @@
from . import myaccount

View File

@@ -1,43 +0,0 @@
<?xml version="1.0" encoding="utf-8"?>
<odoo>
<template id="ticket_priority_widget_template" name="Priority Widget Template">
<span t-attf-class="o_priority_star fa fa-star#{'' if ticket.priority >= ticket_priority else '-o'}" t-attf-title="Priorité: {{'Très haute' if ticket.priority == '3' else 'Haute' if ticket.priority == '2' else 'Moyenne' if ticket.priority == '1' else 'Basse'}}" />
</template>
<template id="ticket_priority_3_stars_template" name="Priority 3 Stars Widget Template">
<t t-call="helpdesk_portal_ticket_custom.ticket_priority_widget_template">
<t t-set="ticket_priority" t-value="'1'"/>
</t>
<t t-call="helpdesk_portal_ticket_custom.ticket_priority_widget_template">
<t t-set="ticket_priority" t-value="'2'"/>
</t>
<t t-call="helpdesk_portal_ticket_custom.ticket_priority_widget_template">
<t t-set="ticket_priority" t-value="'3'"/>
</t>
</template>
<!-- Ticket portal list -->
<template id="portal_ticket_list_inherit" inherit_id="helpdesk_mgmt.portal_ticket_list" priority="1">
<!-- Add priority field -->
<xpath expr="//thead/tr/th[2]" position="after">
<th>Priorité</th>
</xpath>
<xpath expr="//tbody/t/tr/td[2]" position="after">
<td>
<t t-call="helpdesk_portal_ticket_custom.ticket_priority_3_stars_template">
</t>
</td>
</xpath>
</template>
<template id="portal_ticket_form_inherit" inherit_id="helpdesk_mgmt.portal_helpdesk_ticket_page">
<xpath expr="//div[@class='col-9']" position="before">
<div>
<t t-call="helpdesk_portal_ticket_custom.ticket_priority_3_stars_template">
</t>
</div>
</xpath>
</template>
</odoo>

View File

@@ -2,20 +2,38 @@
helpdesk_portal_ticket_enriched_description_form
================================================
Add fieds in ticket creation portal form to enrich description content.
Add fields in ticket creation portal form to enrich description content.
This module extends the ``helpdesk_mgmt`` portal ticket creation form by
replacing the single description field with three structured fields:
* **Description**: Main description of the issue or request, with a placeholder
guiding the user to be precise and describe how to reproduce any bug/error.
* **Access**: Optional field for providing a link toward the error or additional
information.
* **Bug report**: Optional field to paste the complete error message (e.g., Odoo
error code).
When the ticket is submitted, these three fields are automatically concatenated
into a single formatted HTML description with labeled sections (DESCRIPTION,
ACCESS, BUG REPORT).
Installation
============
Use Odoo normal module installation procedure to install
`helpdesk_portal_ticket_enriched_description_form`.
This module depends on ``helpdesk_mgmt`` which must be available.
# Known issues / Roadmap
None yet.
Bug Tracker
===========
Bugs are tracked on `our issues website <https://github.com/elabore-coop/helpdesk-tools/issues>`\_. In case of
Bugs are tracked on `our issues website <https://git.elabore.coop/Elabore/helpdesk-tools/issues>`\_. In case of
trouble, please check there if your issue has already been
reported. If you spotted it first, help us smashing it by providing a
detailed and welcomed feedback.

View File

@@ -3,7 +3,7 @@
{
"name": "helpdesk_portal_ticket_enriched_description_form",
"version": "16.0.1.0.1",
"version": "18.0.1.0.0",
"author": "Elabore",
"website": "https://elabore.coop",
"maintainer": "Stéphan Sainléger",

View File

@@ -1,24 +1,52 @@
import odoo.http as http
# Copyright 2024 Stéphan Sainléger (Elabore)
# License AGPL-3.0 or later (http://www.gnu.org/licenses/agpl).
from odoo import _
from odoo.addons.helpdesk_mgmt.controllers.main import HelpdeskTicketController
def build_enriched_description(small_description=None, access=None, bug_report=None):
"""
Build a formatted HTML description from the enriched form fields.
:param small_description: Main description of the issue
:param access: Link or access information
:param bug_report: Error message or bug report details
:return: Formatted HTML string
"""
description = ""
if small_description:
description = "<b>%s</b><br/>%s" % (_("DESCRIPTION:"), small_description)
if access:
description = "%s<br/><br/><b>%s</b><br/>%s" % (
description,
_("ACCESS:"),
access,
)
if bug_report:
description = "%s<br/><br/><b>%s</b><br/>%s" % (
description,
_("BUG REPORT:"),
bug_report,
)
return description
class HelpdeskTicketControllerDescription(HelpdeskTicketController):
def _prepare_submit_ticket_vals(self, **kw):
# Pop enriched fields and build description BEFORE calling super
# to avoid parent's plaintext2html(kw.get("description")) crashing on None
small_description = kw.pop("small_description", None)
access = kw.pop("access", None)
bug_report = kw.pop("bug_report", None)
description = build_enriched_description(
small_description=small_description,
access=access,
bug_report=bug_report,
)
# Set description in kw for parent, using a placeholder to avoid
# plaintext2html issues - we'll overwrite the result anyway
kw["description"] = ""
res = super()._prepare_submit_ticket_vals(**kw)
description = ""
if kw.get("small_description", False):
description = (
description + "<b>%s</b><br/>" % _(u"DESCRIPTION:") + kw["small_description"]
)
del kw["small_description"]
if kw.get("access", False):
description = description + "<br/><br/><b>%s</b><br/>" % _(u"ACCESS:") + kw["access"]
del kw["access"]
if kw.get("bug_report", False):
description = (
description + "<br/><br/><b>%s</b><br/>" % _(u"BUG REPORT:") + kw["bug_report"]
)
del kw["bug_report"]
res.update({"description": description})
res["description"] = description
return res

View File

@@ -4,44 +4,18 @@
#
msgid ""
msgstr ""
"Project-Id-Version: Odoo Server 16.0\n"
"Project-Id-Version: Odoo Server 18.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-07-08 12:26+0000\n"
"PO-Revision-Date: 2025-07-08 12:26+0000\n"
"POT-Creation-Date: 2026-03-17 14:30+0000\n"
"PO-Revision-Date: 2026-03-17 14:30+0000\n"
"Last-Translator: \n"
"Language-Team: \n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: \n"
"Plural-Forms: \n"
#. module: helpdesk_portal_ticket_enriched_description_form
#: model_terms:ir.ui.view,arch_db:helpdesk_portal_ticket_enriched_description_form.helpdesk_create_ticket_description
msgid ""
"<span class=\"col-md-7 col-sm-8\">Be precise. If there is a bug/error, please describe\n"
" how to reproduce it</span>"
msgstr ""
"<span class=\"col-md-7 col-sm-8\">Soyez précis. Si vous avez une erreur, merci de décrire\n"
" comment la reproduire.</span>"
#. module: helpdesk_portal_ticket_enriched_description_form
#: model_terms:ir.ui.view,arch_db:helpdesk_portal_ticket_enriched_description_form.helpdesk_create_ticket_description
msgid ""
"<span class=\"col-md-7 col-sm-8\">Link toward error or additional "
"information</span>"
msgstr ""
"<span class=\"col-md-7 col-sm-8\">Lien vers l'erreur ou des informations "
"complémentaires</span>"
#. module: helpdesk_portal_ticket_enriched_description_form
#: model_terms:ir.ui.view,arch_db:helpdesk_portal_ticket_enriched_description_form.helpdesk_create_ticket_description
msgid ""
"<span class=\"col-md-7 col-sm-8\">Paste here the complete error message (ex: error\n"
" code Odoo)</span>"
msgstr ""
"<span class=\"col-md-7 col-sm-8\">Copier ici le message d'erreur complet (ex: code\n"
" d'erreur Odoo)</span>"
#. module: helpdesk_portal_ticket_enriched_description_form
#. odoo-python
#: code:addons/helpdesk_portal_ticket_enriched_description_form/controllers/main.py:0
@@ -54,6 +28,11 @@ msgstr "ACCÈS :"
msgid "Access"
msgstr "Accès"
#. module: helpdesk_portal_ticket_enriched_description_form
#: model_terms:ir.ui.view,arch_db:helpdesk_portal_ticket_enriched_description_form.helpdesk_create_ticket_description
msgid "Be precise. If there is a bug/error, please describe how to reproduce it"
msgstr "Soyez précis. Si vous avez une erreur, merci de décrire comment la reproduire."
#. module: helpdesk_portal_ticket_enriched_description_form
#. odoo-python
#: code:addons/helpdesk_portal_ticket_enriched_description_form/controllers/main.py:0
@@ -76,4 +55,14 @@ msgstr "DESCRIPTION :"
#. module: helpdesk_portal_ticket_enriched_description_form
#: model_terms:ir.ui.view,arch_db:helpdesk_portal_ticket_enriched_description_form.helpdesk_create_ticket_description
msgid "Description"
msgstr ""
msgstr "Description"
#. module: helpdesk_portal_ticket_enriched_description_form
#: model_terms:ir.ui.view,arch_db:helpdesk_portal_ticket_enriched_description_form.helpdesk_create_ticket_description
msgid "Link toward error or additional information"
msgstr "Lien vers l'erreur ou des informations complémentaires"
#. module: helpdesk_portal_ticket_enriched_description_form
#: model_terms:ir.ui.view,arch_db:helpdesk_portal_ticket_enriched_description_form.helpdesk_create_ticket_description
msgid "Paste here the complete error message (ex: error code Odoo)"
msgstr "Copier ici le message d'erreur complet (ex: code d'erreur Odoo)"

View File

@@ -4,10 +4,10 @@
#
msgid ""
msgstr ""
"Project-Id-Version: Odoo Server 16.0\n"
"Project-Id-Version: Odoo Server 18.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-07-08 12:29+0000\n"
"PO-Revision-Date: 2025-07-08 12:29+0000\n"
"POT-Creation-Date: 2026-03-17 14:30+0000\n"
"PO-Revision-Date: 2026-03-17 14:30+0000\n"
"Last-Translator: \n"
"Language-Team: \n"
"MIME-Version: 1.0\n"
@@ -15,27 +15,6 @@ msgstr ""
"Content-Transfer-Encoding: \n"
"Plural-Forms: \n"
#. module: helpdesk_portal_ticket_enriched_description_form
#: model_terms:ir.ui.view,arch_db:helpdesk_portal_ticket_enriched_description_form.helpdesk_create_ticket_description
msgid ""
"<span class=\"col-md-7 col-sm-8\">Be precise. If there is a bug/error, please describe\n"
" how to reproduce it</span>"
msgstr ""
#. module: helpdesk_portal_ticket_enriched_description_form
#: model_terms:ir.ui.view,arch_db:helpdesk_portal_ticket_enriched_description_form.helpdesk_create_ticket_description
msgid ""
"<span class=\"col-md-7 col-sm-8\">Link toward error or additional "
"information</span>"
msgstr ""
#. module: helpdesk_portal_ticket_enriched_description_form
#: model_terms:ir.ui.view,arch_db:helpdesk_portal_ticket_enriched_description_form.helpdesk_create_ticket_description
msgid ""
"<span class=\"col-md-7 col-sm-8\">Paste here the complete error message (ex: error\n"
" code Odoo)</span>"
msgstr ""
#. module: helpdesk_portal_ticket_enriched_description_form
#. odoo-python
#: code:addons/helpdesk_portal_ticket_enriched_description_form/controllers/main.py:0
@@ -48,6 +27,11 @@ msgstr ""
msgid "Access"
msgstr ""
#. module: helpdesk_portal_ticket_enriched_description_form
#: model_terms:ir.ui.view,arch_db:helpdesk_portal_ticket_enriched_description_form.helpdesk_create_ticket_description
msgid "Be precise. If there is a bug/error, please describe how to reproduce it"
msgstr ""
#. module: helpdesk_portal_ticket_enriched_description_form
#. odoo-python
#: code:addons/helpdesk_portal_ticket_enriched_description_form/controllers/main.py:0
@@ -70,4 +54,14 @@ msgstr ""
#. module: helpdesk_portal_ticket_enriched_description_form
#: model_terms:ir.ui.view,arch_db:helpdesk_portal_ticket_enriched_description_form.helpdesk_create_ticket_description
msgid "Description"
msgstr ""
msgstr ""
#. module: helpdesk_portal_ticket_enriched_description_form
#: model_terms:ir.ui.view,arch_db:helpdesk_portal_ticket_enriched_description_form.helpdesk_create_ticket_description
msgid "Link toward error or additional information"
msgstr ""
#. module: helpdesk_portal_ticket_enriched_description_form
#: model_terms:ir.ui.view,arch_db:helpdesk_portal_ticket_enriched_description_form.helpdesk_create_ticket_description
msgid "Paste here the complete error message (ex: error code Odoo)"
msgstr ""

View File

@@ -0,0 +1,4 @@
# Copyright 2024 Stéphan Sainléger (Elabore)
# License AGPL-3.0 or later (http://www.gnu.org/licenses/agpl).
from . import test_controller

View File

@@ -0,0 +1,116 @@
# Copyright 2024 Stéphan Sainléger (Elabore)
# License AGPL-3.0 or later (http://www.gnu.org/licenses/agpl).
from odoo.tests.common import TransactionCase, tagged
from ..controllers.main import build_enriched_description
@tagged("post_install", "-at_install")
class TestBuildEnrichedDescription(TransactionCase):
"""Test cases for the build_enriched_description utility function."""
def test_all_fields(self):
"""Test that all three fields are correctly concatenated."""
result = build_enriched_description(
small_description="This is the main description",
access="https://example.com/error",
bug_report="Error 500: Internal Server Error",
)
self.assertIn("<b>DESCRIPTION:</b>", result)
self.assertIn("This is the main description", result)
self.assertIn("<b>ACCESS:</b>", result)
self.assertIn("https://example.com/error", result)
self.assertIn("<b>BUG REPORT:</b>", result)
self.assertIn("Error 500: Internal Server Error", result)
def test_description_only(self):
"""Test with only the description field filled."""
result = build_enriched_description(
small_description="Only description provided",
)
self.assertIn("<b>DESCRIPTION:</b>", result)
self.assertIn("Only description provided", result)
self.assertNotIn("ACCESS:", result)
self.assertNotIn("BUG REPORT:", result)
def test_description_and_access(self):
"""Test with description and access fields filled."""
result = build_enriched_description(
small_description="Description text",
access="https://link.com",
)
self.assertIn("<b>DESCRIPTION:</b>", result)
self.assertIn("Description text", result)
self.assertIn("<b>ACCESS:</b>", result)
self.assertIn("https://link.com", result)
self.assertNotIn("BUG REPORT:", result)
def test_description_and_bug_report(self):
"""Test with description and bug report fields filled."""
result = build_enriched_description(
small_description="Description text",
bug_report="Traceback error here",
)
self.assertIn("<b>DESCRIPTION:</b>", result)
self.assertIn("Description text", result)
self.assertNotIn("ACCESS:", result)
self.assertIn("<b>BUG REPORT:</b>", result)
self.assertIn("Traceback error here", result)
def test_access_only(self):
"""Test with only the access field filled."""
result = build_enriched_description(
access="https://link.com",
)
self.assertNotIn("DESCRIPTION:", result)
self.assertIn("<b>ACCESS:</b>", result)
self.assertIn("https://link.com", result)
self.assertNotIn("BUG REPORT:", result)
def test_bug_report_only(self):
"""Test with only the bug report field filled."""
result = build_enriched_description(
bug_report="Error message",
)
self.assertNotIn("DESCRIPTION:", result)
self.assertNotIn("ACCESS:", result)
self.assertIn("<b>BUG REPORT:</b>", result)
self.assertIn("Error message", result)
def test_access_and_bug_report(self):
"""Test with access and bug report fields filled (no description)."""
result = build_enriched_description(
access="https://link.com",
bug_report="Error message",
)
self.assertNotIn("DESCRIPTION:", result)
self.assertIn("<b>ACCESS:</b>", result)
self.assertIn("https://link.com", result)
self.assertIn("<b>BUG REPORT:</b>", result)
self.assertIn("Error message", result)
def test_empty(self):
"""Test with no fields filled."""
result = build_enriched_description()
self.assertEqual(result, "")
def test_html_structure(self):
"""Test that the HTML structure is correctly formatted with line breaks."""
result = build_enriched_description(
small_description="Desc",
access="Link",
bug_report="Error",
)
# Check that sections are separated by double line breaks
self.assertIn("<br/><br/><b>ACCESS:</b>", result)
self.assertIn("<br/><br/><b>BUG REPORT:</b>", result)

View File

@@ -15,10 +15,9 @@
name="small_description"
style="min-height: 120px"
required="True"
placeholder="Be precise. If there is a bug/error, please describe how to reproduce it"
/>
</div>
<span class="col-md-7 col-sm-8">Be precise. If there is a bug/error, please describe
how to reproduce it</span>
</div>
<div class="form-group">
<label
@@ -31,9 +30,9 @@
class="form-control"
type="text"
name="access"
placeholder="Link toward error or additional information"
/>
</div>
<span class="col-md-7 col-sm-8">Link toward error or additional information</span>
</div>
<div class="form-group">
<label
@@ -46,11 +45,11 @@
class="form-control"
name="bug_report"
style="min-height: 120px"
placeholder="Paste here the complete error message (ex: error code Odoo)"
/>
</div>
<span class="col-md-7 col-sm-8">Paste here the complete error message (ex: error
code Odoo)</span>
</div>
<div class="mb-3" />
</xpath>
</template>
</odoo>

View File

@@ -0,0 +1,64 @@
====================================
Helpdesk Portal Ticket List Defaults
====================================
Customize default filter, sort and groupby for the helpdesk portal ticket list.
This module changes the default behavior of the ticket list in the portal:
- **Default filter**: Shows only open tickets (instead of all tickets)
- **Default groupby**: Groups tickets by stage (instead of no grouping)
- **Default sort**: By date (unchanged, but now overridable)
It also adds an "Open" filter option that wasn't available in the base module.
# Extending
Other modules can easily override the defaults by inheriting the controller
and overriding the dedicated methods:
```python
from odoo.addons.helpdesk_portal_ticket_list_defaults.controllers.main import (
CustomerPortalHelpdeskDefaults,
)
class MyCustomDefaults(CustomerPortalHelpdeskDefaults):
def _ticket_get_default_filterby(self):
return "all" # Show all tickets by default
def _ticket_get_default_groupby(self):
return "category" # Group by category instead of stage
```
# Installation
Use Odoo normal module installation procedure to install
`helpdesk_portal_ticket_list_defaults`.
# Known issues / Roadmap
None yet.
# Bug Tracker
Bugs are tracked on `our issues website <https://git.elabore.coop/Elabore/helpdesk-tools/issues>`_.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.
# Credits
## Contributors
- Stéphan Sainléger
## Funders
The development of this module has been financially supported by:
- Elabore (https://elabore.coop)
## Maintainer
This module is maintained by Elabore.

View File

@@ -0,0 +1,3 @@
# License AGPL-3.0 or later (http://www.gnu.org/licenses/agpl).
from . import controllers

View File

@@ -0,0 +1,20 @@
# Copyright 2024 Joris Scampucci (Elabore)
# License AGPL-3.0 or later (http://www.gnu.org/licenses/agpl).
{
"name": "Helpdesk Portal Ticket List Defaults",
"version": "18.0.1.0.0",
"author": "Elabore",
"website": "https://elabore.coop",
"maintainer": "Joris Scampucci",
"license": "AGPL-3",
"category": "Helpdesk",
"summary": "Customize default filter, sort and groupby for portal ticket list.",
"depends": [
"helpdesk_mgmt",
],
"data": [],
"installable": True,
"auto_install": False,
"application": False,
}

View File

@@ -0,0 +1,3 @@
# License AGPL-3.0 or later (http://www.gnu.org/licenses/agpl).
from . import main

View File

@@ -1,3 +1,6 @@
# Copyright 2024 Joris Scampucci (Elabore)
# License AGPL-3.0 or later (http://www.gnu.org/licenses/agpl).
from collections import OrderedDict
from operator import itemgetter
@@ -6,19 +9,44 @@ from odoo.http import request
from odoo.osv.expression import AND
from odoo.tools import groupby as groupbyelem
from odoo.addons.portal.controllers.portal import CustomerPortal
from odoo.addons.helpdesk_mgmt.controllers.myaccount import CustomerPortalHelpdesk
from odoo.addons.portal.controllers.portal import pager as portal_pager
class CustomerPortalHelpdesk(CustomerPortal):
_inherit = "helpdesk_mgmt.myaccount"
class CustomerPortalHelpdeskDefaults(CustomerPortalHelpdesk):
"""Customize default values for ticket list filters in portal."""
@http.route(
["/my/tickets", "/my/tickets/page/<int:page>"],
type="http",
auth="user",
website=True,
)
def _ticket_get_default_sortby(self):
"""Return default sort field. Override to customize."""
return "date"
def _ticket_get_default_filterby(self):
"""Return default filter key. Override to customize."""
return "open"
def _ticket_get_default_groupby(self):
"""Return default groupby field. Override to customize."""
return "stage"
def _ticket_get_searchbar_filters(self):
"""Return available filters for ticket list.
Extends OCA filters with an 'open' filter.
Override to add more custom filters.
"""
filters = {
"all": {"label": _("All"), "domain": []},
"open": {"label": _("Open"), "domain": [("closed", "=", False)]},
}
# Add stage filters like OCA does
for stage in request.env["helpdesk.ticket.stage"].search([]):
filters[str(stage.id)] = {
"label": stage.name,
"domain": [("stage_id", "=", stage.id)],
}
return filters
@http.route()
def portal_my_tickets(
self,
page=1,
@@ -32,46 +60,35 @@ class CustomerPortalHelpdesk(CustomerPortal):
**kw,
):
HelpdeskTicket = request.env["helpdesk.ticket"]
# Avoid error if the user does not have access.
if not HelpdeskTicket.check_access_rights("read", raise_exception=False):
if not HelpdeskTicket.has_access("read"):
return request.redirect("/my")
values = self._prepare_portal_layout_values()
searchbar_sortings = self._ticket_get_searchbar_sortings()
searchbar_sortings = dict(
sorted(
self._ticket_get_searchbar_sortings().items(),
key=lambda item: item[1]["sequence"],
)
)
searchbar_filters = {
"all": {"label": _("All"), "domain": []},
"closed": {"label": _("Ouvert"), "domain": [("closed", "=", False)]},
}
for stage in request.env["helpdesk.ticket.stage"].search([]):
searchbar_filters[str(stage.id)] = {
"label": stage.name,
"domain": [("stage_id", "=", stage.id)],
}
searchbar_filters = self._ticket_get_searchbar_filters()
searchbar_inputs = self._ticket_get_searchbar_inputs()
searchbar_groupby = self._ticket_get_searchbar_groupby()
# Apply defaults
if not sortby:
sortby = "date"
sortby = self._ticket_get_default_sortby()
order = searchbar_sortings[sortby]["order"]
if not filterby:
filterby = "closed"
filterby = self._ticket_get_default_filterby()
domain = searchbar_filters.get(filterby, searchbar_filters.get("all"))["domain"]
if not groupby:
groupby = "stage"
groupby = self._ticket_get_default_groupby()
if date_begin and date_end:
domain += [
domain = domain + [
("create_date", ">", date_begin),
("create_date", "<=", date_end),
]
@@ -79,7 +96,7 @@ class CustomerPortalHelpdesk(CustomerPortal):
if not search_in:
search_in = "all"
if search:
domain += self._ticket_get_search_domain(search_in, search)
domain = domain + self._ticket_get_search_domain(search_in, search)
domain = AND(
[
@@ -88,9 +105,7 @@ class CustomerPortalHelpdesk(CustomerPortal):
]
)
# count for pager
ticket_count = HelpdeskTicket.search_count(domain)
# pager
pager = portal_pager(
url="/my/tickets",
url_args={
@@ -120,7 +135,8 @@ class CustomerPortalHelpdesk(CustomerPortal):
group = groupby_mapping.get(groupby)
if group:
grouped_tickets = [
request.env["helpdesk.ticket"].concat(*g) for k, g in groupbyelem(tickets, itemgetter(group))
request.env["helpdesk.ticket"].concat(*g)
for k, g in groupbyelem(tickets, itemgetter(group))
]
elif tickets:
grouped_tickets = [tickets]

View File

@@ -2,12 +2,32 @@
helpdesk_portal_ticket_priority_form
====================================
Add fieds in ticket creation portal form for priority.
Add priority field and display in the helpdesk portal.
This module extends the helpdesk portal to:
- Add a priority selector in the ticket creation form
- Display a 3-star priority widget in the ticket list
- Display the priority widget in the ticket detail page sidebar (after the ticket number)
# Installation
Use Odoo normal module installation procedure to install
`helpdesk_portal_ticket_enriched_description_form`.
`helpdesk_portal_ticket_priority_form`.
# Configuration
No configuration is required. The priority field and widgets are automatically
available once the module is installed.
# Usage
- **Ticket creation**: When creating a new ticket from the portal, users can
select a priority level from a dropdown.
- **Ticket list**: The priority is displayed as a 3-star widget in the tickets
list view.
- **Ticket detail**: The priority widget is shown in the sidebar, just below
the ticket number.
# Known issues / Roadmap
@@ -15,7 +35,7 @@ None yet.
# Bug Tracker
Bugs are tracked on `our issues website <https://github.com/elabore-coop/helpdesk-tools/issues>`\_. In case of
Bugs are tracked on `our issues website <https://git.elabore.coop/Elabore/helpdesk-tools/issues>`\_. In case of
trouble, please check there if your issue has already been
reported. If you spotted it first, help us smashing it by providing a
detailed and welcomed feedback.

View File

@@ -3,7 +3,7 @@
{
"name": "helpdesk_portal_ticket_priority_form",
"version": "16.0.1.0.0",
"version": "18.0.1.0.0",
"author": "Elabore",
"website": "https://elabore.coop",
"maintainer": "Stéphan Sainléger",

View File

@@ -48,9 +48,10 @@
<!-- Ticket portal page -->
<template id="portal_helpdesk_ticket_page_priority" name="Ticket Portal Template : Priority"
inherit_id="helpdesk_mgmt.portal_helpdesk_ticket_page">
<xpath expr="//h5/div/span" position="before">
<t
t-call="helpdesk_portal_ticket_priority_form.portal_my_tickets_priority_widget_template" />
<xpath expr="//h2[@t-field='ticket.number']" position="after">
<div class="mt-2">
<t t-call="helpdesk_portal_ticket_priority_form.portal_my_tickets_priority_widget_template" />
</div>
</xpath>
</template>
</odoo>
</odoo>

View File

@@ -2,7 +2,23 @@
helpdesk_portal_timesheet
=========================
Show ticket timesheets in portal view
Show ticket timesheets in portal view.
This module extends the ``helpdesk_mgmt_timesheet`` module by displaying
timesheet entries directly on the portal ticket detail page. It provides:
* A "Timesheets" section on the ticket portal page showing all logged time
entries.
* A table displaying for each timesheet line:
* Date
* Employee name
* Description
* Time spent (in hours or days depending on the company UoM setting)
* A footer row showing the total time spent on the ticket.
* Automatic filtering of timesheet lines marked as "excluded from sale order"
(using the ``sale_timesheet_line_exclude`` module).
Installation
============
@@ -10,6 +26,13 @@ Installation
Use Odoo normal module installation procedure to install
``helpdesk_portal_timesheet``.
This module depends on:
* ``helpdesk_mgmt_timesheet``: provides the timesheet functionality on helpdesk
tickets.
* ``sale_timesheet_line_exclude``: provides the ability to exclude timesheet
lines from sale orders (excluded lines are not shown in the portal).
Known issues / Roadmap
======================
@@ -18,7 +41,7 @@ None yet.
Bug Tracker
===========
Bugs are tracked on `our issues website <https://github.com/elabore-coop/helpdesk_portal_timesheet/issues>`_. In case of
Bugs are tracked on `our issues website <https://git.elabore.coop/Elabore/helpdesk-tools/issues>`_. In case of
trouble, please check there if your issue has already been
reported. If you spotted it first, help us smashing it by providing a
detailed and welcomed feedback.
@@ -29,13 +52,14 @@ Credits
Contributors
------------
* `Elabore <mailto:contact@elabore.coop>`
* `Laetitia Da Costa <mailto: laetitia.dacosta@elabore.coop>`
* Elabore - `Email <mailto:contact@elabore.coop>`_
* Laetitia Da Costa - `Email <mailto:laetitia.dacosta@elabore.coop>`_
Funders
-------
The development of this module has been financially supported by:
* Elabore (https://elabore.coop)

View File

@@ -3,7 +3,7 @@
{
"name": "helpdesk_portal_timesheet",
"version": "16.0.1.0.1",
"version": "18.0.1.0.0",
"author": "Elabore",
"website": "https://elabore.coop",
"maintainer": "Elabore",

View File

@@ -47,9 +47,10 @@
</tfoot>
</table>
</template>
<!-- Inheritance to display timesheets on the ticket portal page -->
<template id="portal_helpdesk_ticket_page_inherit_timesheet" inherit_id="helpdesk_mgmt.portal_helpdesk_ticket_page" name="Ticket Portal Template with Timesheets">
<xpath expr="//t[@t-set='card_body']" position="inside">
<xpath expr="//div[@id='card_body']" position="inside">
<div class="container mt-4" t-if="ticket.timesheet_ids">
<hr class="mt-4 mb-1"/>
<h5 id="ticket_timesheets" class="mt-2 mb-2" data-anchor="true">Timesheets</h5>

View File

@@ -4,12 +4,35 @@ helpdesk_request_type
Add request type field in helpdesk ticket.
This module extends the ``helpdesk_mgmt`` module by adding a new "Request Type"
concept to categorize tickets. It provides:
* A new ``helpdesk.request.type`` model to define request types with a name and
a sequence for ordering.
* A ``request_type_id`` field on helpdesk tickets.
* Backend views integration:
* Form view: selection widget displayed before tags.
* Kanban view: request type displayed as a badge.
* List view: optional column after the assigned user.
* Search view: filter and group by request type.
* Portal integration:
* Request type displayed on the ticket detail page.
* Request type selection when creating a new ticket from the portal.
* A configuration menu to manage request types (Helpdesk > Configuration >
Request Types) with drag-and-drop ordering.
Installation
============
Use Odoo normal module installation procedure to install
``helpdesk_request_type``.
This module depends on ``helpdesk_mgmt`` which must be abailable.
Known issues / Roadmap
======================
@@ -18,7 +41,7 @@ None yet.
Bug Tracker
===========
Bugs are tracked on `our issues website <https://github.com/elabore-coop/helpdesk-tools/issues>`_. In case of
Bugs are tracked on `our issues website <https://git.elabore.coop/Elabore/helpdesk-tools/issues>`_. In case of
trouble, please check there if your issue has already been
reported. If you spotted it first, help us smashing it by providing a
detailed and welcomed feedback.

View File

@@ -3,7 +3,7 @@
{
"name": "helpdesk_request_type",
"version": "16.0.1.0.1",
"version": "18.0.1.0.0",
"author": "Elabore",
"website": "https://elabore.coop",
"maintainer": "Stéphan Sainléger",

View File

@@ -2,20 +2,20 @@
<odoo>
<record id="helpdesk_request_type_view_tree" model="ir.ui.view">
<field name="name">helpdesk.request.type.view.tree</field>
<field name="name">helpdesk.request.type.view.list</field>
<field name="model">helpdesk.request.type</field>
<field name="arch" type="xml">
<tree string="Request Types" editable="top" default_order="sequence">
<list editable="top" default_order="sequence">
<field name="sequence" widget="handle" />
<field name="name" />
</tree>
</list>
</field>
</record>
<record id="act_helpdesk_request_types_list" model="ir.actions.act_window">
<field name="name">Request Types</field>
<field name="res_model">helpdesk.request.type</field>
<field name="view_mode">tree</field>
<field name="view_mode">list</field>
</record>
<menuitem

View File

@@ -26,7 +26,7 @@
</record>
<record id="ticket_view_tree_request_type" model="ir.ui.view">
<field name="name">helpdesk.ticket.tree.request.type</field>
<field name="name">helpdesk.ticket.list.request.type</field>
<field name="inherit_id" ref="helpdesk_mgmt.ticket_view_tree" />
<field name="model">helpdesk.ticket</field>
<field name="arch" type="xml">

View File

@@ -1,8 +1,8 @@
<?xml version="1.0" encoding="utf-8"?>
<odoo>
<template id="portal_helpdesk_ticket_request_type" name="My Ticket: Request Type"
inherit_id="helpdesk_mgmt.portal_helpdesk_ticket_page" priority="40">
<xpath expr="//div[@name='portal_ticket_col_0']" position="inside">
inherit_id="helpdesk_mgmt.portal_helpdesk_ticket_page" >
<xpath expr="//div[@t-if='ticket.category_id']" position="after">
<div t-if="ticket.request_type_id">
<strong>Request type:</strong>
<span t-field="ticket.request_type_id" />

View File

@@ -2,7 +2,7 @@
# License AGPL-3.0 or later (http://www.gnu.org/licenses/agpl).
{
"name": "helpdesk_ticket_task_domain",
"version": "16.0.1.0.0",
"version": "18.0.1.0.0",
"author": "Elabore",
"website": "https://elabore.coop",
"maintainer": "Quentin Mondot",

View File

@@ -2,12 +2,32 @@
helpdesk_timesheet_exclude_from_sale_order
==========================================
Add exclude_from_sale_order field in ticket's timesheets
Add exclude_from_sale_order field in ticket's timesheets.
This module is a glue module that bridges the ``sale_timesheet_line_exclude``
functionality with the helpdesk ticket timesheet view. It provides:
* The ``exclude_from_sale_order`` checkbox displayed on each timesheet line
in the helpdesk ticket form view.
* Allows users to mark specific timesheet entries as excluded from invoicing
directly from the ticket, without having to navigate to the timesheet or
project views.
This is particularly useful when some time spent on a ticket should not be
billed to the customer (e.g., internal investigation, training, goodwill
gestures).
# Installation
Use Odoo normal module installation procedure to install
`helpdesk_timesheet_exclude_from_sale_order`.
``helpdesk_timesheet_exclude_from_sale_order``.
This module depends on:
* ``helpdesk_mgmt_timesheet``: provides the timesheet functionality on helpdesk
tickets.
* ``sale_timesheet_line_exclude``: provides the ``exclude_from_sale_order``
field on timesheet lines.
# Known issues / Roadmap
@@ -15,7 +35,7 @@ None yet.
# Bug Tracker
Bugs are tracked on `our issues website <https://github.com/elabore-coop/helpdesk-tools/issues>`\_. In case of
Bugs are tracked on [our issues website](https://git.elabore.coop/Elabore/helpdesk-tools/issues). In case of
trouble, please check there if your issue has already been
reported. If you spotted it first, help us smashing it by providing a
detailed and welcomed feedback.

View File

@@ -2,7 +2,7 @@
# License AGPL-3.0 or later (http://www.gnu.org/licenses/agpl).
{
"name": "helpdesk_timesheet_exclude_from_sale_order",
"version": "16.0.1.0.0",
"version": "18.0.1.0.0",
"summary": "Exclude tickets from sale timesheets",
"author": "Boris Gallet, Elabore Coop",
"website": "https://elabore.coop",

View File

@@ -2,14 +2,35 @@
helpdesk_transfer_timesheet_to_task
===================================
This module assigns the field task of the timesheets' ticket to the task linked to the ticket.
Exception : the timesheet is not transfered to the task linked to the ticket if
it has already been invoiced (timesheet_invoice_id != False).
Automatically transfer timesheets from a ticket to its linked task.
This module extends the ``helpdesk_mgmt_timesheet`` module by automatically
transferring timesheet entries when a task is linked to a ticket. It provides:
* An onchange handler on the ``task_id`` field of helpdesk tickets.
* When a task is linked to a ticket, all timesheets from the ticket are
automatically assigned to the task.
* Protection against double invoicing: timesheets that have already been
invoiced (i.e., have a ``timesheet_invoice_id``) are NOT transferred to the
task and remain on the ticket.
This is particularly useful when a ticket is converted to a task and you want
to keep the time tracking history on the task for project management and
invoicing purposes.
# Installation
Use Odoo normal module installation procedure to install
`helpdesk_transfer_timesheets_to_task`.
``helpdesk_transfer_timesheet_to_task``.
This module depends on:
* ``helpdesk_mgmt``: provides the base helpdesk ticket functionality.
* ``helpdesk_mgmt_project``: provides the link between tickets and projects
(including the ``task_id`` field on tickets).
* ``helpdesk_mgmt_timesheet``: provides timesheet functionality on tickets.
* ``sale_timesheet``: provides the invoicing link on timesheets
(``timesheet_invoice_id`` field).
# Known issues / Roadmap
@@ -17,7 +38,7 @@ None.
# Bug Tracker
Bugs are tracked on `our issues website <https://github.com/elabore-coop/helpdesk-tools/issues>`\_. In case of
Bugs are tracked on [our issues website](https://git.elabore.coop/Elabore/helpdesk-tools/issues). In case of
trouble, please check there if your issue has already been
reported. If you spotted it first, help us smashing it by providing a
detailed and welcomed feedback.

View File

@@ -2,7 +2,7 @@
# License AGPL-3.0 or later (http://www.gnu.org/licenses/agpl).
{
"name": "helpdesk_transfer_timesheet_to_task",
"version": "16.0.1.0.0",
"version": "18.0.1.0.0",
"author": "Elabore",
"website": "https://elabore.coop",
"maintainer": "Quentin Mondot",

View File

@@ -2,22 +2,23 @@ from odoo.tests.common import TransactionCase
class TestHelpdeskTicket(TransactionCase):
@classmethod
def setUpClass(cls):
super().setUpClass()
cls.env = cls.env(context=dict(cls.env.context, tracking_disable=True))
cls.HelpdeskTicket = cls.env["helpdesk.ticket"]
cls.ProjectTask = cls.env["project.task"]
cls.AccountAnalyticLine = cls.env["account.analytic.line"]
cls.AccountMove = cls.env["account.move"]
cls.Project = cls.env["project.project"]
def setUp(self):
super(TestHelpdeskTicket, self).setUp()
self.HelpdeskTicket = self.env["helpdesk.ticket"]
self.ProjectTask = self.env["project.task"]
self.AccountAnalyticLine = self.env["account.analytic.line"]
self.AccountMove = self.env["account.move"]
self.Project = self.env["project.project"]
self.project = self.Project.create(
cls.project = cls.Project.create(
{"name": "Test project", "allow_timesheets": True}
)
self.analytic_account = self.project.analytic_account_id
cls.analytic_account = cls.project.analytic_account_id
# Create a sample task
self.task = self.ProjectTask.create(
{"name": "Sample Task", "project_id": self.project.id}
cls.task = cls.ProjectTask.create(
{"name": "Sample Task", "project_id": cls.project.id}
)
def test_timesheet_added_to_linked_task(self):

View File

@@ -3,8 +3,23 @@ helpdesk_user_default_ticket_team
=================================
Automate ticket team attribution when ticket created by portal user.
- configure default team on portal user form view
- assign automatically the new tickets to the team configured in the user's profile.
This module extends the ``helpdesk_mgmt`` module by allowing to configure a
default helpdesk team per user. It provides:
* A new ``default_helpdesk_ticket_team_id`` field on the user form, located in
the Preferences tab.
* Automatic team assignment when a ticket is created:
* If the ticket has no team assigned and has a linked partner.
* The module looks up the portal user associated with the partner.
* If the user has a default helpdesk team configured, it is automatically
assigned to the ticket.
* If the assigned team has a default project, the ticket is also linked to
that project.
This is particularly useful for multi-company or multi-team environments where
portal users should always have their tickets routed to a specific team.
Installation
============
@@ -12,6 +27,11 @@ Installation
Use Odoo normal module installation procedure to install
``helpdesk_user_default_ticket_team``.
This module depends on:
* ``helpdesk_mgmt``: provides the base helpdesk ticket functionality.
* ``helpdesk_mgmt_project``: provides the link between tickets and projects.
Known issues / Roadmap
======================
@@ -20,7 +40,7 @@ None yet.
Bug Tracker
===========
Bugs are tracked on `our issues website <https://github.com/elabore-coop/helpdesk-tools/issues>`_. In case of
Bugs are tracked on `our issues website <https://git.elabore.coop/Elabore/helpdesk-tools/issues>`_. In case of
trouble, please check there if your issue has already been
reported. If you spotted it first, help us smashing it by providing a
detailed and welcomed feedback.
@@ -31,12 +51,13 @@ Credits
Contributors
------------
* Stéphan Sainléger
* Stéphan Sainléger - `Email <mailto:stephan.sainleger@elabore.coop>`_
Funders
-------
The development of this module has been financially supported by:
* Elabore (https://elabore.coop)

View File

@@ -1,3 +1,2 @@
# -*- coding: utf-8 -*-
from . import models

View File

@@ -3,7 +3,7 @@
{
"name": "helpdesk_user_default_ticket_team",
"version": "16.0.1.1.0",
"version": "18.0.1.0.0",
"author": "Elabore",
"website": "https://elabore.coop",
"maintainer": "Stéphan Sainléger",

View File

@@ -1,4 +1,5 @@
from odoo import api, fields, models, tools
from odoo import api, models
class HelpdeskTicket(models.Model):
_inherit = "helpdesk.ticket"

View File

@@ -1,6 +1,9 @@
from odoo import _, api, fields, models
from odoo import fields, models
class Users(models.Model):
_inherit = "res.users"
default_helpdesk_ticket_team_id = fields.Many2one('helpdesk.ticket.team', string='Default Helpdesk Team')
default_helpdesk_ticket_team_id = fields.Many2one(
"helpdesk.ticket.team", string="Default Helpdesk Team"
)