Skip to content

18.0 mig l10n it central journal reportlab #4491

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

Merged

Conversation

jado95
Copy link
Contributor

@jado95 jado95 commented Dec 6, 2024

No description provided.

@SirAionTech SirAionTech added the needs fixing Has conflicts or is failing mandatory CI checks label Dec 9, 2024
@SirAionTech
Copy link
Contributor

/ocabot migration l10n_it_central_journal_reportlab

@OCA-git-bot OCA-git-bot added this to the 18.0 milestone Dec 13, 2024
@OCA-git-bot OCA-git-bot mentioned this pull request Dec 13, 2024
38 tasks
@jado95 jado95 force-pushed the 18.0-MIG-l10n_it_central_journal_reportlab branch 3 times, most recently from daf91c2 to 455372c Compare December 13, 2024 16:35
@SirAionTech SirAionTech removed the needs fixing Has conflicts or is failing mandatory CI checks label Dec 18, 2024
Borruso added a commit to DinamicheAziendali/l10n-italy that referenced this pull request Dec 23, 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.

Manca riferimento del partner, sia su stampa dettagliata che con raggruppamento conti
image

@jado95 jado95 force-pushed the 18.0-MIG-l10n_it_central_journal_reportlab branch from 455372c to 16710b6 Compare January 31, 2025 16:02
Borruso added a commit to DinamicheAziendali/l10n-italy that referenced this pull request Jan 31, 2025
@jado95 jado95 force-pushed the 18.0-MIG-l10n_it_central_journal_reportlab branch 2 times, most recently from f3bf5e3 to eb3d9e2 Compare February 7, 2025 14:13
Copy link
Contributor

@MarcoCalcagni MarcoCalcagni left a comment

Choose a reason for hiding this comment

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

LGTM

@jado95 jado95 force-pushed the 18.0-MIG-l10n_it_central_journal_reportlab branch from eb3d9e2 to 1d94d49 Compare February 14, 2025 11:13
@jado95 jado95 force-pushed the 18.0-MIG-l10n_it_central_journal_reportlab branch from 1d94d49 to 17e6a01 Compare February 28, 2025 16:57
@odooNextev
Copy link
Contributor

Quando viene fatto il merge di questa PR #4530 dovrebbero passare i test

@francesco-ooops
Copy link
Contributor

/ocabot rebase

Borruso and others added 6 commits March 27, 2025 16:18
Currently translated at 88.3% (53 of 60 strings)

Translation: l10n-italy-14.0/l10n-italy-14.0-l10n_it_central_journal_reportlab
Translate-URL: https://translation.odoo-community.org/projects/l10n-italy-14-0/l10n-italy-14-0-l10n_it_central_journal_reportlab/it/
Currently translated at 95.0% (57 of 60 strings)

Translation: l10n-italy-14.0/l10n-italy-14.0-l10n_it_central_journal_reportlab
Translate-URL: https://translation.odoo-community.org/projects/l10n-italy-14-0/l10n-italy-14-0-l10n_it_central_journal_reportlab/it/
Currently translated at 100.0% (60 of 60 strings)

Translation: l10n-italy-16.0/l10n-italy-16.0-l10n_it_central_journal_reportlab
Translate-URL: https://translation.odoo-community.org/projects/l10n-italy-16-0/l10n-italy-16-0-l10n_it_central_journal_reportlab/it/
@OCA-git-bot
Copy link
Contributor

Congratulations, PR rebased to 18.0.

@OCA-git-bot OCA-git-bot force-pushed the 18.0-MIG-l10n_it_central_journal_reportlab branch from 17e6a01 to 94af281 Compare March 27, 2025 16:18
Copy link
Contributor

@primes2h primes2h left a comment

Choose a reason for hiding this comment

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

@eLBati
Copy link
Member

eLBati commented Apr 10, 2025

#4510

In chiamata abbiamo valutato che non riusciremmo adesso con le risorse attuali. Lo riteniamo meno prioritario rispetto a rilasciare la funzionalità sulla 18

Copy link

@gdemarco2esseti gdemarco2esseti left a comment

Choose a reason for hiding this comment

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

Functional Review: Needs fix

Dovrebbe indicare il riferimento al partner e non al numero del documento

Screenshot 2025-04-10 alle 10 21 14

Copy link
Contributor

@monen17 monen17 left a comment

Choose a reason for hiding this comment

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

Grazie della PR!
Grande che hai già schiacciato i commit dei bot 👏
Potresti però includere (nel punto corretto della history) gli ultimi commit della 16.0?
Manca ad esempio 7cc8de8 e diverse traduzioni

@@ -1,3 +1,3 @@
id,name,model_id:id,group_id:id,perm_read,perm_write,perm_create,perm_unlink
access_date_range_group_account_manager,group_account_manager model_date_range,model_date_range,account.group_account_manager,1,1,0,0
access_wizard_giornale_reportlab_manager,access_wizard_giornale_reportlab manager,l10n_it_central_journal_reportlab.model_wizard_giornale_reportlab,,1,1,1,1
access_wizard_giornale_reportlab_manager,access_wizard_giornale_reportlab manager,l10n_it_central_journal_reportlab.model_wizard_giornale_reportlab,account.group_account_manager,1,1,1,1
Copy link
Contributor

Choose a reason for hiding this comment

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

Prima tutti gli utenti avevano questo accesso quindi penso si traduca nell'aggiunta di base.group_user.

Se invece si vuole modificare questo accesso ok, ma va fuori secondo me dallo scope della migrazione di per sé quindi andrebbe come minimo in un commit separato.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

In v18 in teoria non è possibile lasciare il gruppo vuoto.
Anche in call su discord abbiam discusso, e avere un gruppo di contabilità che faccia una stampa contabile, è più corretto che avere un qualsiasi utente che possa farlo

<record id="view_date_range_inherit_tree" model="ir.ui.view">
<field name="name">date.range.tree.inherit</field>
<record id="view_date_range_inherit_list" model="ir.ui.view">
Copy link
Contributor

Choose a reason for hiding this comment

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

Capisco mantenere la coerenza con il tipo di vista, ma per cambiare l'XMLID serve anche una migrazione (vedi https://oca.github.io/openupgradelib/API.html#openupgradelib.openupgrade.rename_xmlids), altrimenti eventuali viste dipendenti potrebbero non trovarlo più.

La soluzione più veloce invece è lasciarlo com'era 😉

Comment on lines 385 to 435
self, move_line_ids, tables, start_row, width_available
self, list_line_not_grouped, tables, start_row, width_available
Copy link
Contributor

Choose a reason for hiding this comment

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

Questa come diverse altre modifiche non mi sembrano proprie di una migrazione, potresti chiarire a cosa servono?
Se non servono per la migrazione andrebbero almeno in un commit separato.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Questa dovrebbe semplicemente chiamare l'arg in modo più chiaro, così come fatto per il metodo grupped

Borruso added a commit to DinamicheAziendali/l10n-italy that referenced this pull request Apr 18, 2025
…eivable/payable accounts, otherwise use entry name
Copy link

@gdemarco2esseti gdemarco2esseti 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

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

Copy link
Contributor

@odooNextev odooNextev left a comment

Choose a reason for hiding this comment

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

LGTM

@eLBati
Copy link
Member

eLBati commented May 23, 2025

Risolti gli ultimi punti aperti

/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

What a great day to merge this nice PR. Let's do it!
Prepared branch 18.0-ocabot-merge-pr-4491-by-eLBati-bump-nobump, awaiting test results.

@OCA-git-bot
Copy link
Contributor

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

@OCA-git-bot OCA-git-bot merged commit 274459d into OCA:18.0 May 23, 2025
6 of 7 checks passed
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.

Terminologia inglese utilizzata non corrisponde alle funzionalità esistenti ed è fuorviante