Skip to content

[18.0][ADD] hr_collective_agreement_partner#1545

Draft
Anxo82 wants to merge 2 commits intoOCA:18.0from
sygel-technology:18.0-add-hr_collective_agreement_partner
Draft

[18.0][ADD] hr_collective_agreement_partner#1545
Anxo82 wants to merge 2 commits intoOCA:18.0from
sygel-technology:18.0-add-hr_collective_agreement_partner

Conversation

@Anxo82
Copy link

@Anxo82 Anxo82 commented Feb 5, 2026

@HaraldPanten @Jaimermaccione

@Anxo82 Anxo82 marked this pull request as draft February 5, 2026 07:37
@Anxo82 Anxo82 force-pushed the 18.0-add-hr_collective_agreement_partner branch from 543a4d8 to 0d6fe51 Compare February 5, 2026 09:00
@Anxo82 Anxo82 force-pushed the 18.0-add-hr_collective_agreement_partner branch from 0d6fe51 to dc2dfd7 Compare February 5, 2026 09:30
Copy link

@NL66278 NL66278 left a comment

Choose a reason for hiding this comment

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

👍 Thank you also for this module. Again a few changes would help adoption.

@Anxo82 Anxo82 force-pushed the 18.0-add-hr_collective_agreement_partner branch from dc2dfd7 to 7076383 Compare February 5, 2026 11:34
@Anxo82
Copy link
Author

Anxo82 commented Feb 5, 2026

@NL66278 the ir.actions.act_window has been moved to its own XML file, and inherited views now keep the original XML-IDs, with the view name updated to include the module name as suggested.
Thanks.

Copy link

@NL66278 NL66278 left a comment

Choose a reason for hiding this comment

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

👍 LGTM

Copy link

@Jaimermaccione Jaimermaccione left a comment

Choose a reason for hiding this comment

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

@Anxo82
The module has been reviewed functionally in a local environment.

The link between company-type partners and collective agreements has been tested and works as expected.

Contact smart button

As a possible improvement, assuming the current access flow is kept (only HR / HR Admin users can create or edit collective agreements), it may be worth adjusting the behavior of the smart button on contacts:

  • The smart button should also be visible when the company has 0 linked agreements, allowing any user (or users with contact permissions) to assign an already existing agreement.
  • From this list, users should not be able to create new agreements, only link an existing one.

If this approach is technically feasible, it would provide a more consistent user experience and reduce confusion between creating agreements and assigning them.

README – usage section

As an additional improvement, it would be good to review and enhance the README usage section.
Based on the changes that may be introduced following these requests, the README could include a clearer and more explicit “usage” section for the module.

Thank you!

@Anxo82 Anxo82 force-pushed the 18.0-add-hr_collective_agreement_partner branch from 7076383 to e299c8d Compare February 10, 2026 10:27
@Anxo82
Copy link
Author

Anxo82 commented Feb 10, 2026

@Jaimermaccione Changes applied.
The smart button is now always visible on the partner form. From the partner’s collective agreements list, existing agreements can be assigned through a dedicated wizard.
Could you review it again?
Thanks

@Jaimermaccione
Copy link

@Anxo82 I have tested the new changes and the behavior matches my expectations.

I have a couple of comments:

1. README – "Authorized users"

In the README you mention:

From the collective agreements list of a contact, authorized users can assign additional collective agreements using the “Select Agreement” button.

Is this restricted to a specific user group? I have not detected any particular access restriction.

I think it is fine if any internal user can assign a collective agreement. If there is no actual group limitation, it might be better to remove the reference to “authorized users” from the README to avoid confusion.


2. Existing assignments are preserved

When it states:

Existing assignments are preserved.

I understand that collective agreements cannot be unlinked from this view, correct?

Would it be possible to add a column allowing users to unlink them? In other standard Odoo models, there is usually a column with an “X” or a trash icon to remove the relation.

I believe it would be appropriate for a user to be able to manage the unlinking of a collective agreement from a contact as well.

Please review this and assess whether the implementation would be reasonably simple.


Thank you.

@Anxo82 Anxo82 force-pushed the 18.0-add-hr_collective_agreement_partner branch from e299c8d to 55d0bcf Compare February 11, 2026 14:30
@Anxo82
Copy link
Author

Anxo82 commented Feb 11, 2026

@Jaimermaccione changes done. Could you review it again?
Thanks

Copy link

@Jaimermaccione Jaimermaccione left a comment

Choose a reason for hiding this comment

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

@Anxo82 I have functionally reviewed the previously discussed changes in a local environment.

The updates have been correctly implemented. It is now possible to remove collective agreements from contacts that already have them assigned.

Additionally, the README wording has been improved to avoid confusion regarding user permissions.

Everything has been verified and works as expected.

LGTM 👍

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants