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

l10n_it_fatturapa_in amount_total_signed sign #3043

Closed
2 tasks
lorenzoallegrucci opened this issue Nov 16, 2022 · 1 comment
Closed
2 tasks

l10n_it_fatturapa_in amount_total_signed sign #3043

lorenzoallegrucci opened this issue Nov 16, 2022 · 1 comment
Assignees
Labels
14.0 16.0 bug hotfix required stale PR/Issue without recent activity, it'll be soon closed automatically.

Comments

@lorenzoallegrucci
Copy link

lorenzoallegrucci commented Nov 16, 2022

Module

l10n_it_fatturapa_in

Describe the bug

Ci sembra che la logica secondo la quale è calcolato il segno di amount_total_signed sia invertita, in quanto normalmente
questo segno è negativo per le fatture fornitori. Invece succede che il segno sia positivo.

To Reproduce

Affected versions:

Steps to reproduce the behavior:

  1. importare una fattura xml che contiene il nodo "arrotondamento"

2022-11-16_11-42

  1. nell'elenco delle fatture fornitori il valore mostrato è positivo anziché essere negativo

Expected behavior
In odoo14, l'elenco delle fatture fornitori mostra il campo "totale documento" con il segno negativo, pertanto ci si aspetta
che anche le fatture fornitori xml importate abbiano il "totale documento" negativo.
Le note credito fornitore avranno invece segno positivo.

@tafaRU tafaRU added the required label Jul 7, 2023
TheMule71 added a commit to TheMule71/l10n-italy that referenced this issue Jul 7, 2023
TheMule71 added a commit to TheMule71/l10n-italy that referenced this issue Jul 7, 2023
@eLBati eLBati changed the title 14.0 l10n_it_fatturapa_in l10n_it_fatturapa_in amount_total_signed sign Aug 16, 2023
Copy link

There hasn't been any activity on this issue in the past 6 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 issue 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 Jun 23, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
14.0 16.0 bug hotfix required stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
2 participants