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

[12.0][FIX] Il fondo ammortizzato nell'anno precedente non considera tutti gli anni precedenti #3010

Conversation

SirTakobi
Copy link
Contributor

@SirTakobi SirTakobi commented Nov 8, 2022

Risolve #3009 per 12.0.

Non ho testato il codice per il report previsional perché nel test il totale mi veniva 0 invece di 1000, nonostante da interfaccia il comportamento sia quello atteso.
Suppongo sia un problema mio che non ne so nulla di cespiti 😅 e creavo il test nel modo sbagliato (in pratica uguale al test esistente, ma con il report di tipo 'previsional').
Ad ogni modo, il codice per il report previsional è identico al codice per il report journal quindi penso sia accettabile anche lasciare con un solo test.

@SirTakobi SirTakobi changed the title Il fondo ammortizzato nell'anno precedente non considera tutti gli anni precedenti [FIX] Il fondo ammortizzato nell'anno precedente non considera tutti gli anni precedenti Nov 8, 2022
@SirTakobi SirTakobi force-pushed the 12.0-fix-assets_management-prev_year_computation branch from a8c1e75 to 144990d Compare November 8, 2022 11:27
@SirTakobi SirTakobi marked this pull request as ready for review November 8, 2022 11:48
@sergiocorato sergiocorato changed the title [FIX] Il fondo ammortizzato nell'anno precedente non considera tutti gli anni precedenti [12.0][FIX] Il fondo ammortizzato nell'anno precedente non considera tutti gli anni precedenti Nov 18, 2022
@sergiocorato
Copy link
Contributor

@SirTakobi grazie, puoi forzare il riavvio dei test?

@sergiocorato
Copy link
Contributor

e aprire la issue per la 14.0, visto che adesso il modulo è migrato e non si era tenuto conto di questa

@SirTakobi SirTakobi force-pushed the 12.0-fix-assets_management-prev_year_computation branch from 144990d to 05ee201 Compare January 12, 2023 09:05
@SirTakobi
Copy link
Contributor Author

@SirTakobi grazie, puoi forzare il riavvio dei test?

Fatto rebase

e aprire la issue per la 14.0, visto che adesso il modulo è migrato e non si era tenuto conto di questa

La issue esisteva già, è #3009: ho aggiornato la parte per 14.0 con ? perché non so se il problema è anche lì

@SirTakobi
Copy link
Contributor Author

@OCA/local-italy-maintainers che ne dite si può mergiare? Grazie!

@eLBati
Copy link
Member

eLBati commented May 3, 2023

/ocabot merge patch

@OCA-git-bot
Copy link
Contributor

This PR looks fantastic, let's merge it!
Prepared branch 12.0-ocabot-merge-pr-3010-by-eLBati-bump-patch, awaiting test results.

OCA-git-bot added a commit that referenced this pull request May 3, 2023
Signed-off-by eLBati
@OCA-git-bot
Copy link
Contributor

It looks like something changed on 12.0 in the meantime.
Let me try again (no action is required from you).
Prepared branch 12.0-ocabot-merge-pr-3010-by-eLBati-bump-patch, awaiting test results.

OCA-git-bot added a commit that referenced this pull request May 3, 2023
Signed-off-by eLBati
@OCA-git-bot
Copy link
Contributor

It looks like something changed on 12.0 in the meantime.
Let me try again (no action is required from you).
Prepared branch 12.0-ocabot-merge-pr-3010-by-eLBati-bump-patch, awaiting test results.

OCA-git-bot added a commit that referenced this pull request May 3, 2023
Signed-off-by eLBati
@OCA-git-bot
Copy link
Contributor

@eLBati your merge command was aborted due to failed check(s), which you can inspect on this commit of 12.0-ocabot-merge-pr-3010-by-eLBati-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.

@SirTakobi SirTakobi force-pushed the 12.0-fix-assets_management-prev_year_computation branch from 05ee201 to f248061 Compare May 8, 2023 09:25
@SirTakobi
Copy link
Contributor Author

@eLBati your merge command was aborted due to failed check(s), which you can inspect on this commit of 12.0-ocabot-merge-pr-3010-by-eLBati-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.

Forse il bot si era stancato di rifare il branch per le nuove modifiche di 12.0.
Ho fatto un rebase per accertarmi che i test siano ok

@OCA-git-bot
Copy link
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

@SirTakobi SirTakobi force-pushed the 12.0-fix-assets_management-prev_year_computation branch from f248061 to 61e3c87 Compare July 7, 2023 13:39
@sergiocorato
Copy link
Contributor

/ocabot merge patch

1 similar comment
@TheMule71
Copy link
Contributor

/ocabot merge patch

@OCA-git-bot
Copy link
Contributor

On my way to merge this fine PR!
Prepared branch 12.0-ocabot-merge-pr-3010-by-sergiocorato-bump-patch, awaiting test results.

@OCA-git-bot
Copy link
Contributor

On my way to merge this fine PR!
Prepared branch 12.0-ocabot-merge-pr-3010-by-TheMule71-bump-patch, awaiting test results.

OCA-git-bot added a commit that referenced this pull request Aug 4, 2023
Signed-off-by sergiocorato
OCA-git-bot added a commit that referenced this pull request Aug 4, 2023
Signed-off-by TheMule71
@OCA-git-bot
Copy link
Contributor

@TheMule71 your merge command was aborted due to failed check(s), which you can inspect on this commit of 12.0-ocabot-merge-pr-3010-by-TheMule71-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.

@OCA-git-bot
Copy link
Contributor

@sergiocorato your merge command was aborted due to failed check(s), which you can inspect on this commit of 12.0-ocabot-merge-pr-3010-by-sergiocorato-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.

@SirTakobi SirTakobi force-pushed the 12.0-fix-assets_management-prev_year_computation branch from 61e3c87 to 51f50a9 Compare August 4, 2023 08:18
@TheMule71
Copy link
Contributor

/ocabot merge patch

@OCA-git-bot
Copy link
Contributor

What a great day to merge this nice PR. Let's do it!
Prepared branch 12.0-ocabot-merge-pr-3010-by-TheMule71-bump-patch, awaiting test results.

@OCA-git-bot OCA-git-bot merged commit 5f20d92 into OCA:12.0 Aug 4, 2023
3 checks passed
@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at c13ff4e. Thanks a lot for contributing to OCA. ❤️

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.

5 participants