[14.0] new module project_consumable #814
Conversation
|
At the time writing it's in a WIP state cf above checklist otherwise reviews and comments are welcome, let me know if you have better idea in naming things ! |
|
[thinking out loud] I've the feeling that end users think more about project than analytic account so I thinks it's important to link to project/tasks and more accurate as many projects could be linked to the same analytic account. I think code could be simpler if we do not link material consumption to project (as a lot of code assume account.analytic.line to be timesheet as long there is project_id defined on the line). Instead we could link to analytic account or new dedicated consumable_project_id/consumable_task_id field 🤔... |
|
creating dedicated consumable_project_id/consumable_task_id won't be a good solution or deport complexity to the reporting/analysis parts... |
petrus-v
force-pushed
the
14.0-project-consumable
branch
from
7fb7e9f
to
c40a69d
Compare
…mpanies Seen in unittest while developed OCA#814 While creating a new company a new project is created with 2 tasks by the hr_timesheet._create_internal_project_task method. Whithout sequence availaible task can't be created and raise un exception as code is null
|
The latest commit 61e6dda is about fixing unit test base on issue found in project_sequence_task, I'll move it in a dedicated PR if test passed ! |
…mpanies Seen in unittest while developed OCA#814 While creating a new company a new project is created with 2 tasks by the hr_timesheet._create_internal_project_task method. Whithout sequence availaible task can't be created and raise un exception as code is null
petrus-v
force-pushed
the
14.0-project-consumable
branch
from
c158dd8
to
ca152ff
Compare
This module give the ability records consumuable product per project to track in your analytic.
petrus-v
force-pushed
the
14.0-project-consumable
branch
from
ca152ff
to
f3bac36
Compare
petrus-v
changed the title
|
There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. |
github-actions
bot
added
the
stale
…mpanies Seen in unittest while developed OCA#814 While creating a new company a new project is created with 2 tasks by the hr_timesheet._create_internal_project_task method. Whithout sequence availaible task can't be created and raise un exception as code is null
…mpanies Seen in unittest while developed OCA#814 While creating a new company a new project is created with 2 tasks by the hr_timesheet._create_internal_project_task method. Whithout sequence availaible task can't be created and raise un exception as code is null
…mpanies Seen in unittest while developed OCA/project#814 While creating a new company a new project is created with 2 tasks by the hr_timesheet._create_internal_project_task method. Whithout sequence availaible task can't be created and raise un exception as code is null
As discussed on https://odoo-community.org/groups/contributors-15/contributors-195985?mode=thread&date_begin=&date_end= here a suggested implementation to follow materials/consumable usages per projects
Depends on #920 (merged) to pass unite tests.deploy in production from june 2021
deploy in may 2022