Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[18.0][MIG] crm_event: Migration to 18.0 #430

Open
wants to merge 20 commits into
base: 18.0
Choose a base branch
from

Conversation

HeliconiaSolutions
Copy link

No description provided.

Jairo Llopis and others added 20 commits February 3, 2025 14:32
This module extends the functionality of CRM opportunities (and leads, if
enabled) to support linking them to event types and to allow you to keep track
of leads interested in an upcoming event of some type.

This is useful if you organize your events based on the amount of people
interested in a certain type of event.

@Tecnativa TT27664

[UPD] Update crm_event.pot

[UPD] README.rst

[ADD] icon.png
- Upstream merged both lead and opportunity form views.

@Tecnativa TT31318
It complies with the requirements and is needed by manifestoo.
The company field isn't mandatory for event types, so we have to check
that a lead auto invites to events available in the company of the lead.

We also have to check the proper base_url for our template. When we have
multi-website we want our customer going to the right link, otherwise
they'd be getting confusing info.

TT36027
Currently translated at 100.0% (40 of 40 strings)

Translation: event-15.0/event-15.0-crm_event
Translate-URL: https://translation.odoo-community.org/projects/event-15-0/event-15-0-crm_event/it/
Currently translated at 100.0% (40 of 40 strings)

Translation: event-15.0/event-15.0-crm_event
Translate-URL: https://translation.odoo-community.org/projects/event-15-0/event-15-0-crm_event/es/
This migration removes the `read_group` for event totals calculation in
the _compute_event_total method because the `seats_available` field in
v17 is not stored (`compute` and `store=False`). This makes `read_group`
unable to correctly process and calculate the value of the
`seats_available` field, as it operates directly on data stored
in the database.
Instead, a manual calculation is implemented which:
- Iterates over the filtered events according to the domain.
- Groups the data by `event_type_id`.
- Calculates the total number of available seats and the number of
events associated with each type.

TT51918
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: event-17.0/event-17.0-crm_event
Translate-URL: https://translation.odoo-community.org/projects/event-17-0/event-17-0-crm_event/
@pedrobaeza
Copy link
Member

/ocabot migration crm_event

@OCA-git-bot OCA-git-bot added this to the 18.0 milestone Feb 3, 2025
@OCA-git-bot OCA-git-bot mentioned this pull request Feb 3, 2025
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants