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

ADD module contract_fixed_discount #1009

Closed

Conversation

damdam-s
Copy link
Member

No description provided.

@damdam-s damdam-s marked this pull request as draft October 19, 2023 12:57
@damdam-s damdam-s force-pushed the 14.0-add_fixed_discount_on_contract_line branch from 30fa2dc to 904c588 Compare October 19, 2023 13:32
@damdam-s damdam-s marked this pull request as ready for review October 20, 2023 13:49
Copy link

@petrus-v petrus-v left a comment

Choose a reason for hiding this comment

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

LGTM

@damdam-s damdam-s force-pushed the 14.0-add_fixed_discount_on_contract_line branch 2 times, most recently from f2bd758 to 41a9d72 Compare October 20, 2023 14:39

<field name="arch" type="xml">
<field name="discount" position="after">
<field name="discount_fixed" optional="hide" />

Choose a reason for hiding this comment

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

testing on runboat :

  • this looks like to manage the popup form view which which don't care about optional
  • so we should add it on the tree view in the contract form view
  • we should probably use same group as the discount fields
  • I think we should change the group to rely on the same one present on sale order: groups="product.group_discount_per_so_line"

Choose a reason for hiding this comment

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

Test on runboat: thanks ❤️

@damdam-s damdam-s force-pushed the 14.0-add_fixed_discount_on_contract_line branch from 4f6e6e5 to 9f80be2 Compare October 23, 2023 08:52
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Feb 25, 2024
@github-actions github-actions bot closed this Mar 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants