-
-
Notifications
You must be signed in to change notification settings - Fork 346
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
[14.0] [IMP] sale_commission_geo_assign #454
[14.0] [IMP] sale_commission_geo_assign #454
Conversation
Hi @eLBati, |
1ee4492
to
9c4cdee
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Functional ok!
This change is both an IMP to features and a clarification of initial behavior (which has been left untouched).
@eLBati good for you?
60aec4d
to
46c519a
Compare
46c519a
to
f925c46
Compare
@pedrobaeza can we merge? |
/ocabot merge minor |
This PR looks fantastic, let's merge it! |
Congratulations, your PR was merged at a1fc50a. Thanks a lot for contributing to OCA. ❤️ |
This PR aims to improve some little things in
sale_commission_geo_assign
.With the current situation it's not really helpful in a situation like: "Agent A has stopped working with our company, so Agent B must be assigned to Agent A's former customers"
To address those things there are several improvements: