-
-
Notifications
You must be signed in to change notification settings - Fork 309
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
[13.0][FIX] mis_builder: add sudo to access field_id due missing permissions (backport) #601
[13.0][FIX] mis_builder: add sudo to access field_id due missing permissions (backport) #601
Conversation
Resolve a permission issue when creating report periods with a user without admin rights.
Hi @sbidoul, |
/ocabot merge patch |
This PR looks fantastic, let's merge it! |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@sbidoul I don't know how to fix this error |
In this version, it's not needed (I would say only 15.0+ requires it), as Odoo removes the ir.model user access. |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
16 similar comments
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
2 similar comments
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
Hi @sbidoul, |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
7 similar comments
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
@sbidoul your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-601-by-sbidoul-bump-patch. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
Backport of #596.