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

[MIG] hr_holidays_leave_auto_approve: Migrated to 10.0 #271

Merged
merged 2 commits into from
Nov 1, 2016
Merged

[MIG] hr_holidays_leave_auto_approve: Migrated to 10.0 #271

merged 2 commits into from
Nov 1, 2016

Conversation

espo-tony
Copy link
Contributor

Migration of the module 'hr_holidays_leave_auto_approve' from V9 to V10.
This module allows the user to define a leave type in order to make the system automatically approving all the leave requests (and leave allocation requests) belonging to that leave type.

@pedrobaeza pedrobaeza mentioned this pull request Oct 28, 2016
58 tasks
@pedrobaeza
Copy link
Member

Please respect commit history following https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-10.0

@espo-tony espo-tony changed the title [10.0][MIG] Module 'hr_holidays_leave_auto_approve': [MIG] hr_holidays_leave_auto_approve: Migrated to 10.0 Oct 28, 2016
@feketemihai feketemihai added this to the 10.0 milestone Nov 1, 2016
Copy link
Member

@feketemihai feketemihai left a comment

Choose a reason for hiding this comment

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

@espo-tony As an improvement to the module, can you make or at least add in readme a roadmap info, which should hide the approve button if the selected holiday status is marked as auto approve...

#. Go on the leave type configuration menu
#. Select the leave type you wish to setup
#. Mark the flag 'Auto Approve'.

Copy link
Member

Choose a reason for hiding this comment

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

@espo-tony Can you make readme complaint, usage with Try me on runbot , credits icon, plus Bug Tracker section...

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@feketemihai ,
Thank you for reviewing this module.
In my latest commit I added the missing informations to the readme file.
As for the approve button, I don't think it's a good idea to hide it when the selected status is marked as auto approve, as it would make the request impossible to approve in the following two cases:

  • The request was performed, but not approved, before that the module was installed (or after that the module was installed but before that the holiday status was marked as auto approve);
  • The administrative user (in contravention with what is suggested in the configuration guide), at the moment of the request creation, doesn't belong to the Holidays/Officer group.

In both cases, as the functionality is intended to work only during the request creation, the approval will never be automatically triggered and, if we hide the button, also the manual approval won't be possible.
To avoid these issues, and because I don't see any drawback in showing the approval button for auto-approval marked requests, I'd prefer to not add this feature. What's your opinion about that?

Copy link
Member

Choose a reason for hiding this comment

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

@espo-tony This was my fear in the PR for 9.0, but it was merge beside taking this in consideration, #258 , it was about launching the validation on write method...but we can leave like this to keep the same behaviour...Thanks for the changes.

@pedrobaeza
Copy link
Member

What about the commit history? It hasn't been respected

@espo-tony
Copy link
Contributor Author

@pedrobaeza
Sorry, it seems I made a mistake somewhere during the process, as indeed I didn't follow the steps that you linked above. In future I will surely take it in account, but for this PR do you have any suggestion about how to fix it?
Thank you in advance.

@pedrobaeza
Copy link
Member

My suggestions are that you start from a clean 10.0 branch, make the steps, and then, copy your final code over the resulting branch, and make a new commit with these changes. Finally, push that branch over this one and you will get everything correct.

aesposito-onestein and others added 2 commits November 1, 2016 12:38
…to define a leave type in order to make the system automatically approving all the leave requests (and leave allocation requests) belonging to that leave type.
@espo-tony
Copy link
Contributor Author

@pedrobaeza ,
Is this correct?

Copy link
Member

@pedrobaeza pedrobaeza left a comment

Choose a reason for hiding this comment

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

Yeah, it seems so. Thanks!

@pedrobaeza pedrobaeza merged commit 6d27891 into OCA:10.0 Nov 1, 2016
sambarros pushed a commit to sambarros/hr that referenced this pull request Jul 26, 2018
[BSSFL-383] Data all, take S3 file
Mraimou pushed a commit to camptocamp/hr that referenced this pull request Nov 25, 2019
BSIBSO-1121 Active field in PO, views improvement
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants