Project Issue - automatic responsible assignment

project_service_profiling
REPOSITORY
REPOSITORYOCA/project
GIT
GIThttps://github.com/OCA/project.git
GIT FOLDER
GIT FOLDERhttps://github.com/OCA/project/tree/6.1/project_service_profiling
VERSION
VERSION 6.1
CATEGORY
CATEGORYProject Management
LICENSE
LICENSELGPL-3
APPLICATION
APPLICATIONNo
AUTO-INSTALLABLE
AUTO-INSTALLABLENo
AUTHORS
AUTHORSOdoo Community Association (OCA), Daniel Reis
MAINTAINERS
MAINTAINERSOdoo Community Association (OCA), Daniel Reis
COMMITTERS
COMMITTERSAlexandre Fayolle, Sylvain LE GAL, Daniel Reis, Pierre Monod
WEBSITE
WEBSITEdaniel.reis@securitas.pt
LAST TRACKING UPDATE
LAST TRACKING UPDATE2026-07-06 00:04:06
ODOO DEPENDENCIES
ODOO DEPENDENCIES odoo/odoo:
    - hr
    - base_setup
    - base
    - mail
    - base_tools
    - resource
    - process
    - board
    - crm
    - base_action_rule
    - base_calendar
    - fetchmail
PYTHON DEPENDENCIES
PYTHON DEPENDENCIES Not have
SYSTEM DEPENDENCIES
SYSTEM DEPENDENCIES Not have
DESCRIPTION
DESCRIPTION
    Automatically assign a responsible when creating a new Issue, or other type of document. 
    Responsible person is looked up on a "profiling" table based on Sales Team and Department.
    "Sales Teams" allow to define different target teams. Originally are ment for Sales people, but here are (re)used also for Service Teams handling Issues, Claims, Tasks, etc.
    Initially was ment to on Issues, but currently it's generic enough to work on any object: crm.case, crm.claim, project.task, etc. 
    This module doesn't even require for Project to be installed. The names used are project related for historic reasons.
    
    Usage:
    - Profiling rules are defined either on Department form or on User form.
    - User is assigned by a Server Action. Example using Project Issues:
                Object:         project.issue.profiling
                Action Type:    Python Code
                Python Code:    self.set_user_id(cr, uid, [context.get('active_id')], 'project.issue', override_flds=['project_id.user_id'], context=context)
    - Server action can be called by an Automated Action or by a Workflow.
    

Code Analysis

Views touched (2)
XML IDNameModelTypeStatus
view_department_form view_department_form_dreisprof hr.department field Inherits hr.view_department_form
view_users_form_reisprof res.users.form.reis res.users notebook Inherits base.view_users_form
Models touched (0)

No models found for this module.