This release is a pre-release and may not be stable for production use.
Project timesheet time control
This module adds a button at account analytic line level to compute the spent time, in minutes, from start date to the current moment.
It improves the domain applied to task field for accommodating to a project flow.
It adds a datetime field that replaces date field in tree view, and write date field with datetime field value.
Finally, it allows to open and close tasks from account analytic lines. The selected closed stage is the first one that is found with the mark “Closed” checked.
Table of contents
Usage
You can access via timesheets:
Go to Timesheets > Timesheet > All Timesheets.
Create a new record.
You will see now that the “Date” field contains also time information.
If you don’t select any “project”, you will be able to select any “task”, opened or not.
Selecting a “task”, the corresponding “project” is filled.
Selecting a “project”, tasks are filtered for only allow to select opened tasks for that project. Remember that an opened task is a task whose stage doesn’t have “Closed” mark checked.
At the end of the line, you will see an stop button.
When you press this button, the difference between “Date” field and the current time, writing this in the field “Duration”.
You can modify the “Date” field for altering the computation of the duration.
Or via tasks:
Go to Project > Search > Tasks.
Click on one existing task or create a new one.
On the “Timesheets” page, you will be able to handle records the same way as you do in the above explanation (except the task selection part, which in this case doesn’t appear as it’s the current one).
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
-
Pedro M. Baeza
Antonio Espinosa
Carlos Dauden
Sergio Teruel
Luis M. ontalba
Ernesto Tejeda
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
This module is part of the OCA/project project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Metadata
1 maintainer
Release files for odoo11-addon-project-timesheet-time-control 11.0.1.2.0.99.dev10
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| odoo11_addon_project_timesheet_time_control-11.0.1.2.0.99.dev10-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Release files / odoo11_addon_project_timesheet_time_control-11.0.1.2.0.99.dev10-py2.py3-none-any.whl
| Download URL | odoo11_addon_project_timesheet_time_control-11.0.1.2.0.99.dev10-py2.py3-none-any.whl |
|---|---|
| Size | 88.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
1e54a4e5d70e2440e175c07eba4ac273fd50f09cd7a8fc68f043786ba36aff8e
|
|
BLAKE2b-256 checksum How to use checksums |
53e1e057b75eb58cb92b69389a805ec672a548149754a3a505314399087f5716
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.5
|
Security for odoo11-addon-project-timesheet-time-control 11.0.1.2.0.99.dev10
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
