Daily updates from Odoo
Navigate
Branch
Tuesday, April 3, 2018
9 changes
Enhancements to existing features
This update improves how Odoo adds and manages followers on records such as projects, HR requests, expenses, maintenance items, calendar events, and learning or event content. It reduces background database work, avoids duplicate follower issues in expense reports, and keeps notifications flowing correctly when people are automatically subscribed.
Original PR description
Task: https://www.odoo.com/web?debug#id=1824616&view_type=form&model=project.task&action=333&active_id=965&menu_id=4720
This change prevents HR Attendance sessions from closing automatically after a week of inactivity by keeping the session alive in the background. This helps employees and managers avoid unexpected interruptions when using attendance-related screens over time.
Original PR description
The session was closing every 7 days for lack of activity. I had a small query running once a day to avoid that. Task: 47216 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Project and timesheet kanban cards now show their action links in more consistent positions. This makes cards easier to scan and reduces layout shifts when different links are available.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
This fixes an issue in Odoo's test utilities where readonly fields in editable line items were incorrectly ignored during simulated form saves. It helps ensure automated tests better match real user behavior in the Odoo client, reducing false failures or missed issues around dynamic form updates.
Original PR description
When trying to make a dynamic onchange, I defined a technical not stored boolean field (`flag` in this PR) that is set to True to mark the line as to be recomputed by the parent. This works fine in the Odoo client. However, when creating a test using the `Form` class, I'm facing to a strange behavior: `flag` is always `False`. The fields views doesn't take care about my field that is not stored, invisible and readonly :disappointed: The problem seems to come from the following line: https://github.com/odoo/odoo/blob/master/odoo/tests/common.py#L937 Thank you in advance! -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue where a single chatter message could appear to create duplicate message counts for the recipient. Users will now see the correct number of messages in their inbox and starred message indicators, reducing confusion around unread or pending communications.
Original PR description
Id #1824534 Issue: https://www.odoo.com/web?#id=1824534&view_type=form&model=project.task&action=327&menu_id=4720 Description of the issue/feature this PR addresses: when one message send through chatter to the recipient, but at the end side(recipient) it show 2 messages. Current behavior before PR: when one message send through chatter to the recipient, but at the end side(recipient) it show 2 messages. Desired behavior after PR is merged: when one message send through chatter to the recipient, but at the end side(recipient) it show correct count of messages. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update adjusts the Accounting module to support a related test correction. It helps keep automated checks reliable, reducing the risk of future accounting changes being blocked or incorrectly validated.
Original PR description
Complement of 802339c12d1984d1f29e574378cd8df2471ab098 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue that prevented sales receipts from being recorded when using journals in a secondary currency. The system now applies the correct positive or negative currency amount depending on whether the receipt is a sale or purchase, so validation works as expected.
Original PR description
… sale
The amount expressed in the secondary currency must be positive when account is debited and negative when account is credited.
Id #1819396
Issue :
https://www.odoo.com/web?#id=1819396&view_type=form&model=project.task&action=327&menu_id=4720
Description of the issue/feature this PR addresses:
- Activate Multi Currency
- Create new sales type journal and set currency(other than company currency)
- Also set debit and credit account in respective currency
- Go to Accounting > Sales Receipt and
- Create new Sales receipt and select the respective journal and try to validate
- You always get the following warning and no any way to record it.
Current behavior before PR:
You always get the following warning and no any way to record it.
Desired behavior after PR is merged:
Works fine with both type of journal with all currency.
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prTimesheet creation now validates fields in a more reliable order, preventing inconsistent error behavior. This helps ensure users receive the correct validation message instead of occasional access-related errors during timesheet entry.
Original PR description
When creating a timesheet, several fields need to be recomputed: - `currency_id` - `group_id` - `department_id` - `is_timesheet` - `validated` When `validated` is computed before the other fields, the recomputation will lead to an `AccessError` because of the rule `hr_timesheet.timesheet_line_rule_user`. Since the test `test_timesheet_validation_user` expects an `AccessError`, the test succeeds. However, from time to time, `validated` is computed last => the `AccessError` is not raised. Actually, a `ValidationError` should be raised in this case (from the `create` override in `timesheet_grid`). Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes inconsistent behavior when users create timesheets by ensuring validation checks happen in the intended order. It helps prevent intermittent errors and makes the expected business validation message appear reliably.
Original PR description
When creating a timesheet, several fields need to be recomputed: - `currency_id` - `group_id` - `department_id` - `is_timesheet` - `validated` When `validated` is computed before the other fields, the recomputation will lead to an `AccessError` because of the rule `hr_timesheet.timesheet_line_rule_user`. Since the test `test_timesheet_validation_user` expects an `AccessError`, the test succeeds. However, from time to time, `validated` is computed last => the `AccessError` is not raised. Actually, a `ValidationError` should be raised in this case (from the `create` override in `timesheet_grid`).