Odoo Changelog — 2024-11-30

Saturday, November 30, 2024

5 changes

Branch: master

1 change

Bug Fixes(1)

Resolved issues and error corrections

[FIX] heldepsk: Team members should be from the team company.

PR #73752

Enterprisemasterhelpdesk

Helpdesk teams can now only include members from the same company as the team. This prevents tickets from being assigned to users who cannot access or see them, improving assignment accuracy in multi-company setups.

Original PR description

[FIX] heldepsk: Team members should be from the team company.

Bug:
You can add a Team Member from another company to a helpdesk team. 

Steps to reproduce: 
- Create two Companies, one User in each company
- In the Helpdesk Team of Company 1 > Automatic Assignement > add also User from Company 2
- Connect to User 2 > he doesn't see the Tickets even if he is assigned to it

Solution:
- filter member_ids by the current company

task-4207465

#helpdesk#multi-company#team assignment

Branch: 18.0

4 changes

Bug Fixes(4)

Resolved issues and error corrections

[FIX] mail: Incoming call pop-ups shouldn't be transparent

PR #188573

Core18.0mail

Incoming call invitation pop-ups now keep a consistent dark background with white text, instead of appearing transparent or switching to a bright style in dark mode. This makes call notifications easier to read and reduces visual discomfort for users using dark theme.

Original PR description

Call invitation was transparent because text-bg-900 is a backend-specific classname style. As a result, the pop-up had no bg-color.

Also the background color and text looks good in white theme: black background with white text. This matches the colors in the call view. In dark theme the colors were inverted: white background and black text. This is unintentional, because this doesn't match call view color that is black color and white text in dark theme too. Also the main advantage of dark theme is to put less eye strain and the inverted colors in dark theme were actually more eye-straining than white theme.

This commit fixes the issue by putting specific color in CSS. These colors should not change with theme: dark theme should keep dark background and white text.

task-4354214

#calls#notifications#dark theme#user interface

[FIX] account: When loading chart template, don't unlink shared records

PR #184450

Core18.0accountMedium

Loading a new chart of accounts for a company no longer deletes accounting records that are shared with other companies. This prevents one company’s setup changes from accidentally disrupting accounting configurations used elsewhere.

Original PR description

When loading a chart template on a root company, we check whether any journal items have already been created for the company, and if not, we delete the existing accounting configuration before loading the new CoA.

However, we must take care in the case of records that are shared between several companies, to just unlink them from the active company, rather than delete them (which would affect other companies as well).

This commit fixes that.

task-none

#accounting#chart of accounts#multi-company

[FIX] social_linkedin: update hashtags link formatting

PR #74611

Enterprise18.0social_linkedinsocial_test_full

LinkedIn hashtag links generated from social posts now use LinkedIn's current link format. This helps ensure hashtags, including edge cases like short or mixed formats, open correctly for users viewing LinkedIn content.

Original PR description

With the current links generated for the hashtags in Linkedin, there's a few corner cases that are not being handled by Linkedin side as we expect it to (ex #FLD), so from 18.0 onwards we should follow the same formatting Linkedin is using nowadays.

Previous link: https://www.linkedin.com/feed/hashtag/FLD2024 
Link after the change: https://www.linkedin.com/feed/hashtag/?keywords=FLD2024

In the previous links you can see the differences between them.

opw-4326960

#linkedin#hashtags#social

[FIX] l10n_mx_edi(_pos): allow global invoices in foreign currencies

PR #73646

Enterprise18.0l10n_mx_edil10n_mx_edi_posMedium

Mexican global invoices can now be created from invoices or POS orders in a foreign currency, as long as all selected documents use the same currency. This prevents unnecessary blocking for valid USD or other foreign-currency transactions while still avoiding mixed-currency global invoices.

Original PR description

### Steps to reproduce the issue:

1. Activate Mexican Localization and switch to Mexican company
2. Create a POS Order or an Invoice in USD
3. Select the Order/Invoice and create a Global Invoice
4. Receive the error:

>     You can't process orders having a foreign currency.
or
>     You can't process invoices having a foreign currency.

### Explanation:

The intended behaviour, blocking multicurrency on Global Invoicing, was explained as an interdiction on foreign currencies.

### Fix reasoning:

Intended behaviour is to block the user when all `pos.order` or `account.move` do not have the same `currency_id`.

opw-4302180

#mexico#global-invoicing#foreign-currency#pos

[FIX] heldepsk: Team members should be from the team company. Bug: You can add a Team Member from another company to a helpdesk team. Steps to reproduce: - Create two Companies, one User in each company - In the Helpdesk Team of Company 1 > Automatic Assignement > add also User from Company 2 - Connect to User 2 > he doesn't see the Tickets even if he is assigned to it Solution: - filter member_ids by the current company task-4207465

Call invitation was transparent because text-bg-900 is a backend-specific classname style. As a result, the pop-up had no bg-color. Also the background color and text looks good in white theme: black background with white text. This matches the colors in the call view. In dark theme the colors were inverted: white background and black text. This is unintentional, because this doesn't match call view color that is black color and white text in dark theme too. Also the main advantage of dark theme is to put less eye strain and the inverted colors in dark theme were actually more eye-straining than white theme. This commit fixes the issue by putting specific color in CSS. These colors should not change with theme: dark theme should keep dark background and white text. task-4354214

When loading a chart template on a root company, we check whether any journal items have already been created for the company, and if not, we delete the existing accounting configuration before loading the new CoA. However, we must take care in the case of records that are shared between several companies, to just unlink them from the active company, rather than delete them (which would affect other companies as well). This commit fixes that. task-none

With the current links generated for the hashtags in Linkedin, there's a few corner cases that are not being handled by Linkedin side as we expect it to (ex #FLD), so from 18.0 onwards we should follow the same formatting Linkedin is using nowadays. Previous link: https://www.linkedin.com/feed/hashtag/FLD2024 Link after the change: https://www.linkedin.com/feed/hashtag/?keywords=FLD2024 In the previous links you can see the differences between them. opw-4326960

### Steps to reproduce the issue: 1. Activate Mexican Localization and switch to Mexican company 2. Create a POS Order or an Invoice in USD 3. Select the Order/Invoice and create a Global Invoice 4. Receive the error: > You can't process orders having a foreign currency. or > You can't process invoices having a foreign currency. ### Explanation: The intended behaviour, blocking multicurrency on Global Invoicing, was explained as an interdiction on foreign currencies. ### Fix reasoning: Intended behaviour is to block the user when all `pos.order` or `account.move` do not have the same `currency_id`. opw-4302180