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

[FIX] Righe negative, note e sezioni in fattura fornitore con inversione contabile #3505

Merged

Conversation

SirTakobi
Copy link
Contributor

@SirTakobi SirTakobi commented Jul 26, 2023

Corregge #3503 e #3504 per 14.0.

@eLBati
Copy link
Member

eLBati commented Dec 4, 2023

/ocabot rebase

@OCA-git-bot
Copy link
Contributor

Congratulations, PR rebased to 14.0.

@eLBati
Copy link
Member

eLBati commented Mar 1, 2024

/ocabot rebase

@OCA-git-bot
Copy link
Contributor

Congratulations, PR rebased to 14.0.

@OCA-git-bot OCA-git-bot force-pushed the 14.0-fix-l10n_it_reverse_charge-note_line branch from e4bfc30 to 9edc2f9 Compare March 1, 2024 08:13
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 Jul 21, 2024
@SirAionTech
Copy link
Contributor

/ocabot rebase

Otherwise bills having description lines raise an error when confirmed
Otherwise bills having negative lines raise an error when confirmed
@OCA-git-bot
Copy link
Contributor

Congratulations, PR rebased to 14.0.

@OCA-git-bot OCA-git-bot force-pushed the 14.0-fix-l10n_it_reverse_charge-note_line branch from 9edc2f9 to e48104b Compare August 23, 2024 12:23
Copy link
Contributor

@sergiocorato sergiocorato left a comment

Choose a reason for hiding this comment

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

C'è un motivo per mantenere 2 commit separati?

@SirAionTech
Copy link
Contributor

C'è un motivo per mantenere 2 commit separati?

Sì un commit gestisce le righe descrittive e l'altro le righe negative
image
ognuno dei due problemi poi ha la sua issue dedicata, quindi volendo si può portare avanti solo una delle due.

@github-actions github-actions bot removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Aug 25, 2024
Copy link

@MaurizioPellegrinet MaurizioPellegrinet left a comment

Choose a reason for hiding this comment

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

Test funzionale: OK

@SirAionTech
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 14.0-ocabot-merge-pr-3505-by-SirAionTech-bump-patch, awaiting test results.

@OCA-git-bot OCA-git-bot merged commit e687f99 into OCA:14.0 Sep 2, 2024
7 checks passed
@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at 4c19d38. 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
7 participants