Skip to content
Snippets Groups Projects
  1. Jun 15, 2020
    • Rémy Voet (ryv)'s avatar
      [FIX] (purchase_)mrp(_account): fix order stats button MO · 38c37578
      Rémy Voet (ryv) authored
      Task: 2241471
      38c37578
    • yhu-odoo's avatar
      [REF] mrp: update MO according to "To Comsume" · 5311f01e
      yhu-odoo authored
      Previously, when we upate the "Quantity to Produce" on a MO, we update
      the components to consume according to the BOM we use. After this
      commit, we now update the components according their current number set
      on the MO.
      
      For example, if we have a MO to use x component A to produce y product
      B. When we update the number y to z, the number of A we want to consume
      will be updated from x to x / y * z, regardless of the setting on the
      BOM. If multiple components are used, all components will be updated
      according to this rule.
      
      Task: 2241471
      5311f01e
    • Tiffany Chang (tic)'s avatar
      [REF] mrp: update MO lock/unlock settings · 48672703
      Tiffany Chang (tic) authored
      This commit updates 4 features related to a MO being locked/unlocked.
      
      1. Manufacturing orders are by default unlocked. A new configuration
      setting has been added so users can set the default to be locked.
      This setting only applies to new manufacturing orders after the setting
      has been changed.
      
      2. A MO now shows the same button options regardless if it is
      locked/unlocked ('scrap', 'cancel', 'unreserve')
      
      3. Workers can always change "Consumed Quantities"/"Produced" when
      clicking on a component/finished product line unless state=Done and MO
      is_locked. This includes adding new components/finished products.
      
      4. Workers can now change "To Consume" quantity when clicking on a
      component line, unlocked, and not in states 'Done' or 'Cancel'.
      
      This is part of specification 6-Lock/Unlock of overall Editing in MO
      form and backorders task.
      
      Task: 2241471
      48672703
    • Arnold Moyaux's avatar
      [FIX] stock: No warning when consuming a dozen SN · acb3150c
      Arnold Moyaux authored
      On a move line tracked by serial number. Moving two pieces for
      a serial number trigger a warning explaining that the quantity
      should be 1 or 0. However modify the unit of measure from unit to
      dozen is not a problem.
      
      task-2241471
      acb3150c
    • Arnold Moyaux's avatar
      [FIX] mrp: add move with different company · 71964c20
      Arnold Moyaux authored
      Currently the related on the property use the company in the context and
      not on the current object. It implies that a raw move created on the MO
      form view will have the wrong destination location and trigger the
      check company error.
      
      Use a compute instead of related.
      
      task-2241471
      71964c20
    • Simon Lejeune's avatar
      [REF] mrp: move `plan_from` to a wizard · b0a905a4
      Simon Lejeune authored
      task-2241471
      b0a905a4
    • Rémy Voet (ryv)'s avatar
      [FIX] purchase_mrp: fix count MO in case of MTO · 421d2d21
      Rémy Voet (ryv) authored
      task-2241471
      421d2d21
    • Arnold Moyaux's avatar
      [REF] mrp: workorder onchange · 182f1b8e
      Arnold Moyaux authored
      Create the workorders at the onchange when setting the bom and not a
      "plan" anymore.
      
      task-2241471
      182f1b8e
    • Rémy Voet (ryv)'s avatar
      [REF] mrp: review consumption allowing · 5011ec52
      Rémy Voet (ryv) authored
      Now, by default, a Bill of Material have a flexible
      consumption instead of strict consumption. Also
      add new consumption choice: a flexible consumption
      but with a warning when the bom isn't respected.
      Also, now, the strict (a new warning option) consumption
      is checked only when we try to mark as done the MO.
      
      task-2241471
      5011ec52
    • William Henrotin's avatar
      [REF] mrp: no more produce wizard · 0e2765f5
      William Henrotin authored
      Use a view similar as the pickings one.
      
      task-2241471
      0e2765f5
    • Simon Lejeune's avatar
      [REF] stock: allow using _set_quantity_done in onchanges · 1b642128
      Simon Lejeune authored
      task-2241471
      1b642128
    • Simon Lejeune's avatar
      [FIX] stock: move: allow writing the same quantity done · 93156e7c
      Simon Lejeune authored
      ..even if multiple move lines already exists.
      
      task-2241471
      93156e7c
    • Simon Lejeune's avatar
      [FIX] stock: quantity done compute · 02359fd7
      Simon Lejeune authored
      mismatch on the move lines used by the compute.
      
      task-2241471
      02359fd7
    • Simon Lejeune's avatar
      [FIX] stock: done quantity and reservation compute in onchange · bd250eb1
      Simon Lejeune authored
      Following v13, newId records are instances of NewID and are ignored from
      any `read_group` call. This breaks an important feature: when encoding a
      stock move line (thus, in an onchange context), the `quantity_done` field
      of stock move should be recomputed.
      
      task-2241471
      bd250eb1
    • Rémy Voet (ryv)'s avatar
      [REF] mrp: backorder mechanism · 53252608
      Rémy Voet (ryv) authored
      Allow to "backorder" a production, meaning create another manufacturing
      order with the quantity remaining to produce. We also use the
      reservation of the first order on the next ones by using
      `post_inventory` on the first one and moving the newly created stock
      moves to the backorder.
      
      We introduce a wizard similar to the one in stock.
      Backorders have a sub-sequence.
      Backorders are linked together through the procurement group.
      We allow creating a backorder even if workorders are running by closing
      them, the backorder will call `button_plan` and create its own.
      
      task-2241471
      53252608
    • Simon Lejeune's avatar
      [REF] mrp: remove routing model · c660770e
      Simon Lejeune authored
      Set the operations directly on the Bill of Material.
      Duplicate the demo data where a routing was shared.
      Adapt the tests.
      
      Remove the following feature:
          - set the same routing on parent and kit child bom
          - when planning, if the component of the kit have the same operation
            than a component of the parent bom, merge these operations
      
      task-2241471
      c660770e
    • Laurent Smet's avatar
      [REF] account: journal items reconciliation (part 1/2) · beccf82e
      Laurent Smet authored
      
      This commits refactors the code of the reconciliation, in order to facilitate the process of complex use cases, namely multi-currencies or cash-basis-taxes related (see details below). It also prepares the code for a second refactoring where we will save on each journal items the amount_currency and currency_id field (even in case of operation made in company currency), also in the sake of simplification.
      
      1) Multi-currencies:
      - the account.partial.reconcile model now will have dedicated columns to specify the amount of the partial reconciliation in the debit_line_id currency and the credit_line_id currency. That comes in handy when dealing with journal items having different secondary currencies, but also allows some simplification.
      - residual_amount_currency computation changed accordingly
      - moved models account.full.reconcile and account.partial.reconcile in their dedicated .py file
      
      2) Cash basis taxes
      - cash basis entries now handle correctly rounding errors to make sure the exact amount of gets reported when the reconciliation becomes full.
      - the account for the base amount of cash basis entries has to be set, now, on the company instead of on each cash basis tax.
      - that new 'property' field can be set at the CoA installation via the field property_cash_basis_base_account_id of account.chart.template, or going through the accounting settings.
      
      Was task task: 2243420
      Was PR #50308
      
      Related: odoo/upgrade#1121
      Related: odoo/enterprise#10252
      Signed-off-by: default avatarQuentin De Paoli (qdp) <qdp@openerp.com>
      beccf82e
    • Laurent Smet's avatar
      [FIX] sale_stock: Fix test depending of 'account' running at_install · f074772d
      Laurent Smet authored
      Since the chart template is loaded post_install, a test depending of the accounting
      must always be run post_install.
      f074772d
  2. May 29, 2020
    • Antoine Prieels's avatar
      [IMP] pos_six: Upgrade TIM JavaScript SDK · 3a2d6984
      Antoine Prieels authored
      
      Upgrade the TIM JavaScript SDK to the latest version (4.6.0).
      The version Six gave us initially (3.8.1) didn't return any error
      message. We now have some (ugly) error messages that could at least
      help the cashier understand where the problem comes from (e.g.
      "timCommunicationFailure", "cardholderStop", etc.).
      
      closes odoo/odoo#52181
      
      Taskid: 2267818
      Signed-off-by: default avatarpimodoo <pimodoo@users.noreply.github.com>
      3a2d6984
  3. Jun 15, 2020
  4. Jun 11, 2020
    • Thibault Francois's avatar
      [FIX] timer, hr_timesheet: Fix _compute_display_timer_buttons · ab487982
      Thibault Francois authored
      
      mixin method should not return in the middle of the loop
      Use the value updated on the record instead
      
      super() is called with self at every iteration
      which is not very efficient and can be wrong
      
      Solution call super for each specific record
      and only when needed
      
      write is not a good practice in compute method
      
      closes odoo/odoo#52858
      
      X-original-commit: 7e19ed98d18305370b5c14edd3d310cfea5df714
      Related: odoo/enterprise#11100
      Signed-off-by: default avatarYannick Tivisse (yti) <yti@odoo.com>
      ab487982
  5. Jun 02, 2020
  6. Jun 12, 2020
  7. Jun 15, 2020
  8. Jun 12, 2020
  9. Jun 15, 2020
  10. Jun 03, 2020
  11. Jun 12, 2020
    • Kevin Baptiste's avatar
      [IMP] base: new widgets in partner list view · 6267d597
      Kevin Baptiste authored
      
      Use the new widgets in the list view of res_partner.
      
      closes odoo/odoo#52897
      
      Taskid: 2274257
      Signed-off-by: default avatarYannick Tivisse (yti) <yti@odoo.com>
      6267d597
    • Nicolas Lempereur's avatar
      [FIX] web_editor: translatable after pasted translation · a8e9a818
      Nicolas Lempereur authored
      
      Fixes same issue as b836e00d but for `<div/>` tag.
      
      When we translate html content, all text and (currently) this subset of
      inline tags are allowed inside translations: 'abbr', 'b', 'bdi', 'bdo',
      'br', 'cite', 'code', 'data', 'del', 'dfn', 'em', 'font', 'i', 'ins',
      'kbd', 'keygen', 'mark', 'math', 'meter', 'output', 'progress', 'q',
      'ruby', 's', 'samp', 'small', 'span', 'strong', 'sub', 'sup', 'time',
      'u', 'var', 'wbr', 'text'.
      
      In b836e00d an issue was fixed that `<p/>` would possibly get inside
      translation when copy-pasting, testing some scenario in current chromium
      browser (83.0) it seems the pasted content contains `<div/>` tags.
      
      opw-2259367
      opw-2260711
      closes #52592
      
      closes odoo/odoo#52932
      
      X-original-commit: eed9fb77
      Signed-off-by: default avatarNicolas Lempereur (nle) <nle@odoo.com>
      a8e9a818
    • Nicolas Lempereur's avatar
      [FIX] sale: have online salesperson default working · b4b0828e
      Nicolas Lempereur authored
      
      A sales order on the website will have as salesperson:
      
      - the contact salesperson, and if not set
      
      But if it's not a new address, the "Online orders" > "Salesperson" is
      not used.
      
      With this changeset, the "Online orders" > "Salesperson" is used by
      default if there is no salesperson on the partner as was the intention.
      
      opw-2274665
      closes #52933
      
      closes odoo/odoo#52939
      
      X-original-commit: 957361a5
      Signed-off-by: default avatarNicolas Lempereur (nle) <nle@odoo.com>
      b4b0828e
    • oco-odoo's avatar
      [IMP] account: reconciliation models: match amls whose partner's name is... · d49d1e44
      oco-odoo authored
      [IMP] account: reconciliation models: match amls whose partner's name is contained in payment reference
      
      Invoice matching rules now also match account.move.lines based on their partner's name : if the statement line's payment reference contains the first name and last name of its patner (in any order, at any position), we match the move line.
      
      closes odoo/odoo#50083
      
      Related: odoo/enterprise#10166
      Related: odoo/upgrade#1317
      Signed-off-by: default avatarQuentin De Paoli (qdp) <qdp@openerp.com>
      d49d1e44
    • oco-odoo's avatar
      [IMP] account: reconciliation models: introduce partner mapping · faed88d2
      oco-odoo authored
      Partner mapping is a new field defined on invoice matching reconciliation models. It allows defining a mapping between partners and regular expressions. When ran, on a statement line without any partner set, those rules use this mapping to assign a partner to statement lines without any one set, using the regular expressions to match the payment reference of the statement line.
      
      It is important to note that the mapped partner will only be set to the statement line when the reconciliation is actually performed (so, when clicking the validate button, if the matching rule is not auto_reconcile = True), just like with the partner_map.
      faed88d2
    • oco-odoo's avatar
      [IMP] account: introduce a date limit on the application of reconciliation models · 02f7023b
      oco-odoo authored
      This limit is set by the past_months_limit field of reconciliation models. When set, it specifies the number of months in the past to search for matches when using this model. Older move lines will be ignored.
      
      The point of this feature is to exclude too old stuff that we know we won't reconcile (because of import, old misconfiguration, former misuse of some features, ...). It also allows reducing the number of move lines taken into consideration, and solving perfomance issues functionnally by isolating the move lines into smaller periods to reconcile them separately.
      02f7023b
    • oco-odoo's avatar
      [REF] account: reconciliation models: improve performance · cddd132a
      oco-odoo authored
      When opening the reconciliation widget and calling the matching rules, instead of calling all the rules in a single huge SQL query and then iterating on all the statement lines to match them with the results, we now first group the lines per applicable model and each time call a distinct (but way smaller) query for each group, stopping trying other rules for a statement line when one returns candidates. More queries are performed, but they are way more simple.
      cddd132a
    • Laurent Stukkens (LTU)'s avatar
      [IMP] web_editor: scroll smoothly when dragging snippets · ab72fe6c
      Laurent Stukkens (LTU) authored
      Part of https://github.com/odoo/odoo/pull/51236
      
      
      task-2176020
      
      closes odoo/odoo#51236
      
      Signed-off-by: default avatarQuentin Smetz (qsm) <qsm@odoo.com>
      ab72fe6c
Loading