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_delivery_note: il destinatario del DDT non corrisponde all'indirizzo di fatturazione quando generato da un ordine di vendita #3990

Open
2 of 3 tasks
sergiocorato opened this issue Feb 26, 2024 · 2 comments · Fixed by #3989
Labels
16.0 bug hotfix needs porting This issue has already been resolved for some version no stale Use this label to prevent the automated stale action from closing this PR/Issue.

Comments

@sergiocorato
Copy link
Contributor

sergiocorato commented Feb 26, 2024

Module

l10n_it_delivery_note

Describe the bug

Quando nell'ordine di vendita l'indirizzo di fatturazione è diverso dal cliente, il DDT collegato riporta il cliente.

To Reproduce

Affected versions:

Steps to reproduce the behavior:

  1. creare un ordine di vendita con cliente, indirizzo di fatturazione e indirizzo di destinazione diversi
  2. creare un DDT dall'OUT
  3. il DDT ha il destinatario uguale al cliente

Expected behavior
Il destinatario del DDT dev'essere uguale all'indirizzo di fatturazione.

Additional context
Add any other context about the problem here. (e.g. OS, Python version, ...)

@francesco-ooops
Copy link
Contributor

@MarcoCalcagni che ne pensi?

@sergiocorato sergiocorato changed the title l10n_it_delivery_note destinatario diverso dall'indirizzo di fatturazione e dal cliente quando generato da un ordine di vendita l10n_it_delivery_note: il destinatario del DDT non corrisponde all'indirizzo di fatturazione quando generato da un ordine di vendita Feb 26, 2024
@francesco-ooops francesco-ooops linked a pull request Feb 27, 2024 that will close this issue
Copy link

github-actions bot commented Sep 1, 2024

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 Sep 1, 2024
@francesco-ooops francesco-ooops added hotfix no stale Use this label to prevent the automated stale action from closing this PR/Issue. and removed stale PR/Issue without recent activity, it'll be soon closed automatically. labels Sep 2, 2024
@francesco-ooops francesco-ooops added the needs porting This issue has already been resolved for some version label Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
16.0 bug hotfix needs porting This issue has already been resolved for some version no stale Use this label to prevent the automated stale action from closing this PR/Issue.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants