-
-
Notifications
You must be signed in to change notification settings - Fork 744
[18.0][MIG] account_receipt_journal #2054
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
base: 18.0
Are you sure you want to change the base?
[18.0][MIG] account_receipt_journal #2054
Conversation
5f91d01
to
add575a
Compare
Hi @Shide, @SirTakobi @eLBati , if applicable, could you check the functionality in the localization? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When you create a receipt, default journal is not set to a receipt journal (happens on sale receipt and purchase receipt).
A receipt journal must be set if is any exclusive to receipts.
The receipt journals are being created by default in the data files included in the module. |
add575a
to
fadc6ee
Compare
Test fix: #2056 |
A receipt Journal must be set when creating a receipt like in v16. |
fadc6ee
to
f752c92
Compare
I fixed the issue so that a receipt journal is selected by default when creating a receipt. |
5a6a855
to
857ea0e
Compare
MT-11039 @moduon |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review result: NOT OK. @rjaraspearhead a revision is required because creating receipts from journal views is inconsistent: in Sales, using “New” inside the journal creates an out_invoice instead of an out_receipt, and in Purchases, creating from Kanban or inside the journal produces a vendor bill (in_invoice) and/or error.
- Test 1: OK — Sale/Purchase Receipt Journals exist with receipts=True and higher sequence than other journals of the same type.
- Test 2: NOK — From Kanban “New” in Sale Receipts Journal creates an out_receipt (OK), but using “New” inside the journal creates a customer invoice (out_invoice) instead of a receipt.


- Test 3: NOK — Creating a purchase receipt from Kanban or inside the journal/list yields a vendor bill (in_invoice) and/or error; expected in_receipt.




- Test 4: OK — In a customer invoice (out_invoice), receipt-only journals are not listed in the Journal selector.
- Test 5: OK — In a customer receipt (out_receipt), only receipt-only journals are listed in the Journal selector.
- Test 6: OK — Journal selector respects move type in general: excludes receipt-only journals for invoices and restricts to them for receipts.
b1b351c
to
f6cfd6a
Compare
@Gelojr Could you please review it? |
f6cfd6a
to
23688d4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review result: NOT OK. Limiting scope to Tests 2 and 3. Test 3 fails
- Test 2: OK — Creating a sales receipt works both from the Sale Receipts Journal Kanban “New” and from the Journal List view; the flow that was previously NOK (creating from inside the journal/list) now behaves as expected.
- Test 3: NOT OK — In Purchases, the “Upload” and “Drag & drop” flows fails

23688d4
to
b4f668a
Compare
@@ -0,0 +1,11 @@ | |||
# Dashboard Kanban View – Pending Items Roadmap |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#2054 (comment)
@Gelojr
I’m leaving test 3 in the roadmap for a future implementation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay. Then I'll approve it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Congratulations on the work @rjaraspearhead. PR approved; current scope is OK, with Test 3 not correct and added to the roadmap for a future implementation.
The following tests were executed:
Test 1: OK — Receipt journals exist (receipts=True) with higher sequence than other journals of the same type.
Test 2: OK — Sales receipt creation works from both the Sale Receipts Journal Kanban “New” and the Journal List view; the flow that was previously NOK from inside the journal/list now behaves as expected.
Test 3: NOT OK — In Purchases, the “Upload” and “Drag & drop” flows do not create an in_receipt (they create a vendor bill or fail); working paths are Kanban “New” and List “New”; added to the roadmap.
Test 4: OK — In a customer invoice (out_invoice), receipt-only journals are not listed in the Journal selector.
Test 5: OK — In a customer receipt (out_receipt), only receipt-only journals are listed in the Journal selector.
Test 6: OK — Journal selector respects the move type overall: excludes receipt-only journals for invoices and restricts to them for receipts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code review
/ocabot migration account_receipt_journal |
/ocabot rebase |
…eipts Ported from l10n_it_corrispettivi
Congratulations, PR rebased to 18.0. |
b4f668a
to
a305275
Compare
Thank you for this migration @rjaraspearhead 😄 ❤️ @loida-vm and @u0f from @moduon Next week we should finish this PR 💪🏼 💘 |
No description provided.