HR Timesheet Sheet
This module supplies a new screen enabling you to manage your work encoding (timesheet) by period. Timesheet entries are made by employees each day. At the end of the defined period, employees submit their validated sheet and the reviewer must then approve submitted entries. Periods are defined in the company forms and you can set them to run monthly, weekly or daily. By default, policy is configured to have HR Officers as reviewers.
Table of contents
Installation
This module relies on:
The OCA module ‘2D matrix for x2many fields’, and can be downloaded from Github: https://github.com/OCA/web/tree/11.0/web_widget_x2many_2d_matrix
Configuration
If you want other default ranges different from weekly, you need to go:
In the menu Configuration -> Settings -> Timesheet Options, and select in Timesheet Sheet Range the default range you want.
When you have a weekly range you can also specify the Week Start Day.
To change who reviews submitted sheets, go to Configuration > Settings > Timesheet Options and configure Timesheet Sheet Review Policy accordingly.
For adding more review policies, look at the hr_timesheet_sheet_policy_xxx extra modules.
To disable sending system emails to reviewers when the status of the sheet changes: #. Go to Settings => Timesheets and check the Don’t send email to Reviewer flag
Usage
If you modify the Details tab, automatically the Summary tab is updated. But if you modify the Summary tab, you need to save in order to have the Details tab updated.
In case you modify the unit amount of both tabs, the Details tab will prevail. If you modify the Summary tab, and you need to do a change in the Details tab, please save before.
Known issues / Roadmap
The timesheet grid is limited to display a max. of 1M cells, due to a limitation of the tree view limit parameter not being able to dynamically set a limit. Since default value of odoo, 40 records is too small, we decided to set 1M, which should be good enough in the majority of scenarios.
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
Miquel Raïch <miquel.raich@forgeflow.com>
Andrea Stirpe <a.stirpe@onestein.nl>
Lois Rilo <lois.rilo@forgeflow.com>
-
Alexey Pelykh <alexey.pelykh@corphub.eu>
Dennis Sluijk <d.sluijk@onestein.nl>
Sunanda Chhatbar <sunanda.chhatbar@initos.com>
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/timesheet 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 odoo14-addon-hr-timesheet-sheet 14.0.1.4.3
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 | Actions Reset |
|---|---|---|---|---|
| odoo14_addon_hr_timesheet_sheet-14.0.1.4.3-py3-none-any.whl | Python 3 | none | any | Details for odoo14_addon_hr_timesheet_sheet-14.0.1.4.3-py3-none-any.whl |
Release files / odoo14_addon_hr_timesheet_sheet-14.0.1.4.3-py3-none-any.whl
| Download URL | odoo14_addon_hr_timesheet_sheet-14.0.1.4.3-py3-none-any.whl |
|---|---|
| Size | 542.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
285eb9f6b6bfd15801ce8f773a93a033dc9a1ea8efb56df4973422fce89f9ac9
|
|
BLAKE2b-256 checksum How to use checksums |
babe80264fcfdacb0f86ce57e9db958c93e3a4cdbe7ee01d830ecbb6aacf5bf1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.10
|
Security for odoo14-addon-hr-timesheet-sheet 14.0.1.4.3
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.
