Skip to content

Conversation

@sergiocorato
Copy link

Description of the issue/feature this PR addresses: missing sale order id on project.project

Current behavior before PR: sql constrains on sale_order_id fail

Desired behavior after PR is merged: sql constrains do not fail

--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Copy link
Contributor

@legalsylvain legalsylvain left a comment

Choose a reason for hiding this comment

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

Lgtm. Thanks

@pedrobaeza pedrobaeza added this to the 12.0 milestone Apr 10, 2020
@pedrobaeza
Copy link
Member

Please explain why is this needed, and modify accordingly openupgrade_analisis_work.txt and maybe module documentation (from Nothing to do to Done if applicable).

@sergiocorato
Copy link
Author

sergiocorato commented Apr 10, 2020

Please explain why is this needed, and modify accordingly openupgrade_analisis_work.txt and maybe module documentation (from Nothing to do to Done if applicable).

This constrains fail because migration in v. 11.0 create the sale_line_id here but in v. 12 is added the field sale_order_id here

Copy link
Contributor

@MiquelRForgeFlow MiquelRForgeFlow left a comment

Choose a reason for hiding this comment

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

squash

@sergiocorato sergiocorato force-pushed the 12.0_fix_sale_timesheet_order branch from 278c008 to d2bd30a Compare April 14, 2020 09:08
@sergiocorato
Copy link
Author

done!

Copy link

@ivantodorovich ivantodorovich left a comment

Choose a reason for hiding this comment

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

Don't know about @pedrobaeza 's comment:

... modify accordingly openupgrade_analisis_work.txt and maybe module documentation (from Nothing to do to Done if applicable).

But otherwise LGTM 👍

@OCA-git-bot
Copy link
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

@pedrobaeza
Copy link
Member

Copy link
Contributor

@legalsylvain legalsylvain left a comment

Choose a reason for hiding this comment

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

@sergiocorato could change the analysis file, regarding @pedrobaeza comment ?

thanks !

@sergiocorato sergiocorato force-pushed the 12.0_fix_sale_timesheet_order branch from d2bd30a to 8ddc9b1 Compare May 1, 2020 12:27
@sergiocorato
Copy link
Author

I missed it, done!

@sergiocorato sergiocorato changed the title [FIX] missing sale_order_id [12.0][FIX] missing sale_order_id May 1, 2020
Copy link
Contributor

@legalsylvain legalsylvain left a comment

Choose a reason for hiding this comment

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

Thanks.

/ocabot merge

@OCA-git-bot
Copy link
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

@legalsylvain
Copy link
Contributor

/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

Hey, thanks for contributing! Proceeding to merge this for you.
Prepared branch 12.0-ocabot-merge-pr-2288-by-legalsylvain-bump-nobump, awaiting test results.

@OCA-git-bot OCA-git-bot merged commit c6e9043 into OCA:12.0 May 1, 2020
@OCA-git-bot
Copy link
Contributor

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

6 participants