Skip to content
Snippets Groups Projects
  1. Jul 29, 2019
  2. Aug 03, 2019
  3. Aug 01, 2019
  4. Jul 30, 2019
    • Jérome Maes's avatar
      [FIX] account: analytic lines access with timesheet manager · ed4d14a3
      Jérome Maes authored
      
      When validating a invoice, the billing user should have access (read) for all analytic
      lines. A problem appears when timesheet is installed, since there is a mismatch with
      ir.rule (a timesheet is an analytic line with a project set).
      The rule "account.analytic.line.billing.user" already exists for this problem, but should
      be extended to work in any case.
      
      To reproduce:
      - set a user as timesheet manager and billing user
      - try to validate an invoice (or post an expense)
      - got an access error with "account.analytic.line.timesheet.manager"
      
      opw-2041615
      
      closes odoo/odoo#35297
      
      Signed-off-by: default avatarJérome Maes (jem) <jem@openerp.com>
      ed4d14a3
  5. Jul 31, 2019
  6. Jul 12, 2019
  7. Jul 16, 2019
  8. Jul 29, 2019
  9. Jul 28, 2019
  10. Jul 26, 2019
  11. Jul 25, 2019
  12. Jul 24, 2019
    • Romain Derie's avatar
      [FIX] web_editor, website: avoid returning children of inactive view · 6a592240
      Romain Derie authored
      
      Before this commit, for the following view tree:
      P (active)
      |
      I (inactive)
      |
      II (active)
      When calling `get_related_views()` on 'P', it would wrongly return 'II'.
      It shouldn't, since its parent 'I' is inactive.
      
      Step to reproduce:
      - Go to /shop
      - Enable ecommerce categories
      - Enable Collapsible Cateogories
      - Disable ecommerce categories
      - Collapsible categories is still shown even if its parent got archived
      
      closes odoo/odoo#35154
      
      Signed-off-by: default avatarJérémy Kersten (jke) <jke@openerp.com>
      6a592240
  13. Jul 25, 2019
    • Arnold Moyaux's avatar
      [FIX] stock: MTO overprocessed move · c8754185
      Arnold Moyaux authored
      
      Error due to other module (e.g. purchase_stock, mrp) that will
      define their own rules in order to merge or not moves together.
      Usecase:
      - Install purchase_stock
      - Create a product MTO + buy with a vendor
      - Create a SO of 1 unit
      - On the PO receive 2 units
      - On the delivery deliver 2 units
      
      It will create an empty delivery and put the entire move in
      a back order.
      
      First issue the extra move is created as a MTO if it's copied from an
      MTO move. So il will trigger all the pull rule. We won't it because it's
      an extra quantity and the rules should be only trigger by the original
      document (SO/MO).
      Also an extra move in a picking do the hypothesis that the original move and
      the extra move will always be merged together. But in the previous
      usecase, the module purchase add the condition that 'created_purchase_line_id'
      and 'purchase_line_id' should be the same in order to merge move.
      'created_purchase_line_id' is also copy=False, so the move and the
      extra move will not be merged. create_extra_move only returns the extra
      move and _action_done only process the moves returned by _create_extra_move.
      It result by an original move not merged and not processed by _action_done,
      it will be automaticaly set in a back order and the extra move is
      processed.
      
      In order to fix it, check if the move and the original move will be
      merged. If not, returns both moves.
      
      opw-2008113
      Close #34005
      
      closes odoo/odoo#34411
      
      Signed-off-by: default avatarSimon Lejeune (sle) <sle@openerp.com>
      c8754185
    • David Dufresne's avatar
      [CLA] signature for ddufresne · 5b80695f
      David Dufresne authored
      
      closes odoo/odoo#35079
      
      Signed-off-by: default avatarMartin Trigaux (mat) <mat@odoo.com>
      5b80695f
  14. Jul 24, 2019
Loading