payload: {"push_id":3784087269,"size":8,"distinct_size":1,"ref":"refs/heads/staging.master","head":"109a07f0e5c654d2712c7b8721d75970777cf7d3","before":"a66ea20287ed16008544007969f4935faa8a8932","commits":[{"sha":"b061644e0c4519f4a45351fa9650a0637e7e18e4","author":{"name":"jem-odoo","email":"6964489703ed973b467c16e75b2abe91a57e12f6@openerp.com"},"message":"[IMP] sale: set company required\n\nThe sales order is a important model. Since it generates invoices and other business\ndocuments, the company_id field should be required as the company must be propagate\nto generated documents.\nMoreover, a sales order without a company raises a error, and we need a company to\ncompute the multi currency rate.\n\nThis commit fixes that bug, by setting the company_id field required on sales order\nand sale order line.\n\nNote: we only simplify the ir.rule of sale.order, and not the one of\nsale.order.line. Indeed, when creating an SOL, the creation is done\nin 2 times by the ORM: first insert, then UPDATE with computed stored\nfields. As company_id of SOL is a stored related, the check access rules\nraises during the inconsistent state (between INSERT and UPDATE,\ncompany_id is False).\nMaybe this will be clean after the big refactoring of the ORM.\n\nTask-1999686","distinct":false,"url":"https://api.github.com/repos/odoo/odoo/commits/b061644e0c4519f4a45351fa9650a0637e7e18e4"},{"sha":"938990f6984d7432842bddaac878f731cf2decf9","author":{"name":"jem-odoo","email":"6964489703ed973b467c16e75b2abe91a57e12f6@openerp.com"},"message":"[IMP] project: company required on task\n\nAs task can be billed, it became a important business model. To avoid mistakes in a multi company\nenvironment, we need to make the company_id field required. Indeed shared task can be problematic\nwith access rights when a employee will log timesheet from another company in a task that is not in\nthe same company as its project.\n\nTo populate this field, we recommend to take the company of task's project, or to fallback on\nthe company of the user that created one.\n\nTask-1999686","distinct":false,"url":"https://api.github.com/repos/odoo/odoo/commits/938990f6984d7432842bddaac878f731cf2decf9"},{"sha":"ddb13a520fdc0be60be05c831b61ba5716d3d891","author":{"name":"jem-odoo","email":"6964489703ed973b467c16e75b2abe91a57e12f6@openerp.com"},"message":"[FIX] sale_timesheet: propagate company\n\nOn Sales order confirmation, a project can be create. The project\ncompany is not correctly propagated: the created project should\nbe in the same company as the SO.\nTo stay consistent, during the sold quantity conversion into the\nplanned hours of a task, we need to use the SO company instead of\nthe one of current user.\n\nTask-1999686","distinct":false,"url":"https://api.github.com/repos/odoo/odoo/commits/ddb13a520fdc0be60be05c831b61ba5716d3d891"},{"sha":"26bc10486eb58ca0adc850c1f0483aff41d689e7","author":{"name":"jem-odoo","email":"6964489703ed973b467c16e75b2abe91a57e12f6@openerp.com"},"message":"[FIX] project: progate company in project on AA creation\n\nWhen allowing timesheet on a project, the project generate\nan analytic account if not given. When creating that account,\nthe company should be the one of the project (origin document)\nrather than the one of the current user.\n\nTask-1999686","distinct":false,"url":"https://api.github.com/repos/odoo/odoo/commits/26bc10486eb58ca0adc850c1f0483aff41d689e7"},{"sha":"ef1afb7b69610fa3ff783751ee544d7a0d020841","author":{"name":"jem-odoo","email":"6964489703ed973b467c16e75b2abe91a57e12f6@openerp.com"},"message":"[FIX] project_timesheet_holidays: multi company fixes\n\nIn a multi company environment, some adjustment must be done:\n- the company of an internal project of a company should be in that company\n- the generate timesheet on holidays validation must be in the company the\ntask (or internal project)\n\nThe company should be correctly propagate to timesheets.\n\nTask-1999686","distinct":false,"url":"https://api.github.com/repos/odoo/odoo/commits/ef1afb7b69610fa3ff783751ee544d7a0d020841"},{"sha":"2511841da1c42622b2d83f2235417bb83d14a76a","author":{"name":"jem-odoo","email":"6964489703ed973b467c16e75b2abe91a57e12f6@openerp.com"},"message":"[IMP] project: company field not in debug mode\n\nWe want to display company_id field on project form view only\nwhen user has multi company access group, like every other\ndocument in Odoo\n\nTask-1999686","distinct":false,"url":"https://api.github.com/repos/odoo/odoo/commits/2511841da1c42622b2d83f2235417bb83d14a76a"},{"sha":"3fc2a27808ca4e4ce74884580543e70537d5ce3b","author":{"name":"Robot Odoo","email":"e5b8af77144c7ab3b64f7d349223922596815c76@odoo.com"},"message":"[MERGE] project, sale_timesheet: multi company fixes\n\nImpacted modules: project, sale, sale_timesheet and project_timesheet_holidays.\n\nSince a5b6f31cf28e5381e1c85f66730bcdb55998e643, the multi company environment is contextualized,\nallowing people to see several company documents at the same time. This reveals\nsome problem in such env.\nTo solve this, we need to force the \"company_id\" field as required on some business\nmodel, and to correctly propagate the company when a document generate another one.\nThe guidelines is to stop using company of current user, but the one of the document\nitself.\n\nSee subcommits for more details.\n\nTask-1999686\n\ncloses odoo/odoo#33739\n\nSigned-off-by: Jérome Maes (jem) <jem@openerp.com>","distinct":false,"url":"https://api.github.com/repos/odoo/odoo/commits/3fc2a27808ca4e4ce74884580543e70537d5ce3b"},{"sha":"109a07f0e5c654d2712c7b8721d75970777cf7d3","author":{"name":"Robot Odoo","email":"e5b8af77144c7ab3b64f7d349223922596815c76@odoo.com"},"message":"force rebuild\n\nuniquifier: yO+V4QjUJqGoum8M","distinct":true,"url":"https://api.github.com/repos/odoo/odoo/commits/109a07f0e5c654d2712c7b8721d75970777cf7d3"}]}
other: {"actor":{"display_login":"robodoo"}}