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

[17.0][FW] fieldservice: multiple ports from 16.0 #1340

Open
wants to merge 17 commits into
base: 17.0
Choose a base branch
from

Conversation

houzefa-abba and others added 9 commits March 7, 2025 12:01
Type mix-up was provoking infinite loops when navigating out of form
views with "next" arrow buttons.

Fixes OCA#1161.
Read-only+required partner field shown in debug mode was preventing
manual creation in debug mode or with OCA module base_technical_features.
Service locations `fsm.location` create a partner `res.partner` through
inheritance.

Before this change, partners could be explicitely typed "fsm_location"
when adding them within children of an existing partner, which in turn
would automatically create service locations on top of them.

But creating a service location by hand would not set that type on the
partner created through inheritance. After this change, all partners
built from service locations are typed the same.

Fixes OCA#1128.
Before this change, service location partners (created through
inheritance) were typed "fsm_location" but did not always have a parent.

When adding them within children of an existing partner, they of course
did have a parent, but not the other way around: they had no parents
when created, through inheritance, upon service location creation.

After this change, service location partners are by default children of
the service location owner partner.

This is only done through defaults but not as related fields, which
would break too much. Therefore, existing partners are not impacted by
this change; only new ones created when creating a service location.

See OCA#1128.
Update scheduled_date_start field not date_start field
@brian10048 brian10048 added this to the 17.0 milestone Mar 7, 2025
@brian10048 brian10048 self-assigned this Mar 7, 2025
@OCA-git-bot
Copy link
Contributor

Hi @max3903,
some modules you are maintaining are being modified, check this out!

@brian10048 brian10048 force-pushed the oca-port-fieldservice-16.0-to-17.0-90539d branch 2 times, most recently from d208fd9 to a1542d7 Compare March 8, 2025 02:12
brian10048 and others added 7 commits March 7, 2025 21:19
compute method should depend on fields used in the calculation
Improve fsm.category parent/child relationship and optimize for search and views
Silences the following warning:

WARNING ? odoo.models: parent_path field on model 'fsm.category'
should have unaccent disabled. Add `unaccent=False`
to the field definition.
@brian10048 brian10048 force-pushed the oca-port-fieldservice-16.0-to-17.0-90539d branch 3 times, most recently from 5685b3e to a57d184 Compare March 10, 2025 15:27
Copy link
Member

@rvalyi rvalyi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(code review only)

@brian10048 brian10048 force-pushed the oca-port-fieldservice-16.0-to-17.0-90539d branch from c0652c5 to 1a8cce4 Compare March 10, 2025 16:21
@brian10048
Copy link
Contributor Author

@victoralmau whenever I introduce this commit a425291 the tests hang up on test_fsm_order.py . I'm not too familiar with freeze_time, is there something that should be done differently?

@victoralmau
Copy link
Member

@victoralmau whenever I introduce this commit a425291 the tests hang up on test_fsm_order.py . I'm not too familiar with freeze_time, is there something that should be done differently?

Ok, I see, the way to solve it is the following:

  • Remove freeze_time from class TestFSMOrder.
  • Add freeze_time in the tests that require it.

Actually this “problem” is not explained anywhere, but I have discovered it recently and it happens when tests are run post-install.

@brian10048
Copy link
Contributor Author

@victoralmau that was it! Thank you!

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.

8 participants