TIP: You can type at any time to perform a new search.
Project Issue - automatic responsible assignment
project_service_profiling · OCA/project
Security findings
Migration considerations
- Imports from the old `openerp` namespace: renamed to `odoo` since Odoo 10.0. migration-openerp-import · source
- For a target of Odoo 10.0+: use the `__manifest__.py` manifest name instead of `__openerp__.py`. The filename alone does not establish module age or compatibility. migration-openerp-manifest · source
hr_department— Class 'hr_department' still inherits from the old-style `osv.osv` API: rewrite it against `models.Model`/`models.TransientModel`/`models.AbstractModel` - the old `osv`/`orm` API was removed entirely in modern Odoo. migration-old-api-base · sourcehr_department— Class 'hr_department' declares `_columns` as a plain dict: old-style field/default declarations, replace with `fields.X(...)` class attributes and `default=`. migration-old-style-fields · sourceproject_issue_profiling— Class 'project_issue_profiling' still inherits from the old-style `osv.osv` API: rewrite it against `models.Model`/`models.TransientModel`/`models.AbstractModel` - the old `osv`/`orm` API was removed entirely in modern Odoo. migration-old-api-base · sourceproject_issue_profiling— Class 'project_issue_profiling' declares `_columns` as a plain dict: old-style field/default declarations, replace with `fields.X(...)` class attributes and `default=`. migration-old-style-fields · sourceres_users— Class 'res_users' still inherits from the old-style `osv.osv` API: rewrite it against `models.Model`/`models.TransientModel`/`models.AbstractModel` - the old `osv`/`orm` API was removed entirely in modern Odoo. migration-old-api-base · sourceres_users— Class 'res_users' declares `_columns` as a plain dict: old-style field/default declarations, replace with `fields.X(...)` class attributes and `default=`. migration-old-style-fields · source
Migration review checklist, not a compatibility verdict. No target version is selected: apply version-specific advice only when migrating to that version or later.
- Repository
- OCA/project · module folder · Try on Runboat
- Module version
- 6.1
- Category
- Project Management
- Folder size
- 0.01 MB
- License
- LGPL-3
- Application
- No
- Auto-installable
- No
- Website
- daniel.reis@securitas.pt
- Last tracking update
- 2026-08-07 06:51:51
- Authors
- Odoo Community Association (OCA), Daniel Reis
- Maintainers
- Odoo Community Association (OCA), Daniel Reis
- Committers
- Alexandre Fayolle, Sylvain LE GAL, Daniel Reis, Pierre Monod
- Odoo dependencies
- Python dependencies
- None
- System dependencies
- None
- Required by
- None
- 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 ID | Name | Model | Type | Status |
|---|---|---|---|---|
view_department_form |
view_department_form_dreisprof | hr.department | form | Inherits hr.view_department_form |
view_users_form_reisprof |
res.users.form.reis | res.users | form | Inherits base.view_users_form |
HTTP endpoints (0)
No HTTP endpoints found for this module.
Models touched (0)
No models found for this module.