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

[16.0][MIG] sale_order_invoicing_finished_task: Migration to version 16.0 #2513

Merged

Conversation

Yadier-Tecnativa
Copy link
Contributor

@Tecnativa TT43245

@Yadier-Tecnativa Yadier-Tecnativa force-pushed the 16.0-mig-sale_order_invoicing_finished_task branch 3 times, most recently from 896a21c to df03fc4 Compare May 17, 2023 23:42
@Yadier-Tecnativa
Copy link
Contributor Author

ping @pedrobaeza
the runboat failed but for other module

odoo.sql_db: bad query: UPDATE "project_project" SET "last_update_id" = 6, "last_update_status" = 'on_track', "write_date" = '2023-05-18T00:18:28.061410'::timestamp, "write_uid" = 1 WHERE id IN (1)
ERROR: insert or update on table "project_project" violates foreign key constraint "project_project_last_update_id_fkey"
DETAIL:  Key (last_update_id)=(6) is not present in table "project_update".

Comment on lines 44 to 45
if "invoiceable" in vals:
self.mapped("sale_line_id")._compute_qty_delivered()
Copy link
Member

@hildickethan hildickethan Jun 6, 2023

Choose a reason for hiding this comment

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

should this not be added to the depends of said compute? instead of forcing it in the write

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

@Yadier-Tecnativa Yadier-Tecnativa force-pushed the 16.0-mig-sale_order_invoicing_finished_task branch 4 times, most recently from c074e26 to f6689b8 Compare June 7, 2023 18:51
sergio-teruel and others added 20 commits July 11, 2023 14:50
* [10.0][ADD] sale_order_invoicing_finished_task: New module

* [10.0][IMP] sale_order_invoicing_finished_task: Toggle invoiceable flag in task.

* [10.0][FIX] sale_order_invoicing_finished_task: Not invoiceable status

* [10.0][IMP] sale_order_invoicing_finished_task: check invoice policy

* Add files for README

* Update README.rst

* Change some format issues in README

* Change license to AGPL and improve readme

* Update __manifest__.py

Add Camptocamp as author

* [10.0][FIX] sale_order_invoicing_finished_task: Overwrite create and write methods because the stage_id field onchange not trigger in a form view with statusbar widget

* [10.0][IMP] sale_order_invoicing_finished_task: Add tests
When the product has an invoicing policy Ordered Quantity, setting the task
as Invoiceable will set the delivered qty on the sale order line to the ordered quantity.
…e_stock

This field is declared in module `sale_stock`, which is not a dependency,
but this also makes no sense for tasks to filter on that field.
There were several records with value not totally determined that can cause test to fail
on integration test:

* No employee linked to the user.
* No UoM for service product.
* Unknown company timesheet UoM.

This commit sets these data for avoiding problems, and also remove a non existing field
assignation for removing the warning.
…dated properly in kanban view drag and drop

TT27765
Co-Authored-By: Nikul Chaudhary <nikul.chaudhary.serpentcs@gmail.com>
Previous parent view doesn't depend on the view that adds the field
project_id, so we need to inherit from the proper view.

As `sale_timesheet` depends on `sale_project`, no extra dependency needs
to be added at manifest level.
@Yadier-Tecnativa Yadier-Tecnativa force-pushed the 16.0-mig-sale_order_invoicing_finished_task branch 2 times, most recently from f8cdbe8 to 1d6d472 Compare July 12, 2023 18:10
@Yadier-Tecnativa
Copy link
Contributor Author

ping @chienandalu , @stefan-tecnativa please review.

the runboat failed:
dropdb: error: database removal failed: ERROR: database "bb2163fb2-7082-4b60-a6a0-08f04b71e626" is being accessed by other users
DETAIL: There is 1 other session using the database.

@Yadier-Tecnativa Yadier-Tecnativa force-pushed the 16.0-mig-sale_order_invoicing_finished_task branch 3 times, most recently from 28f9b3f to 763ec5d Compare July 18, 2023 19:31
@Yadier-Tecnativa Yadier-Tecnativa force-pushed the 16.0-mig-sale_order_invoicing_finished_task branch from 763ec5d to 6e12d22 Compare July 18, 2023 20:46
@pedrobaeza
Copy link
Member

/ocabot migration sale_order_invoicing_finished_task
/ocabot merge nobump

@OCA-git-bot OCA-git-bot added this to the 16.0 milestone Sep 26, 2023
@OCA-git-bot
Copy link
Contributor

On my way to merge this fine PR!
Prepared branch 16.0-ocabot-merge-pr-2513-by-pedrobaeza-bump-nobump, awaiting test results.

@OCA-git-bot OCA-git-bot mentioned this pull request Sep 26, 2023
96 tasks
@OCA-git-bot OCA-git-bot merged commit f0c8a10 into OCA:16.0 Sep 26, 2023
5 of 7 checks passed
@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at fa0344a. 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
Development

Successfully merging this pull request may close these issues.

10 participants