Skip to content
Snippets Groups Projects
  1. May 03, 2019
  2. Feb 21, 2019
  3. May 02, 2019
  4. Apr 26, 2019
    • Denis Ledoux's avatar
      b1193004
    • Gert Pellin's avatar
      [FIX] point-of-sale: discount line on ticket · 26c4acc7
      Gert Pellin authored
      
      Before this fix an extra line with the price without discount will be
      printed even if there is no discount on the product.
      
      After this fix the line will only be printed if there is a discount.
      
      The error occured due to the use of t-else instead of t-elif.
      
      closes odoo/odoo#32989
      
      Signed-off-by: default avatarNicolas Martinelli (nim) <nim@odoo.com>
      26c4acc7
    • Xavier Morel's avatar
      [IMP] base: avoid unnecessary exists in Contact HTML formatter · 617ba288
      Xavier Morel authored
      
      Protactively checking exists() seems unnecessary, it's likely that the
      widget would be called on an empty recordset but seems very unlikely
      that it'll be called on a missing record. The commit which added the
      exists() call performs significant refactoring/rewrite and doesn't
      explain why this exists() call would be useful.
      
      Since exists is not cached and qweb field converters are not batched,
      saves a large number of queries when formatting a series of addresses
      e.g. with 99 hr.job, /jobs goes from ~170 queries and ~100ms spent in
      SQL to ~70 queries and ~60ms spent in SQL.
      
      Though the total performance improvement is very limited as even with
      odoo/odoo#32985 the endpoint takes ~700ms (with the aforementioned 99
      hr.job visible to the current user).
      
      closes odoo/odoo#32986
      
      Signed-off-by: default avatarXavier Morel (xmo) <xmo@odoo.com>
      617ba288
  5. Apr 25, 2019
  6. Apr 30, 2019
  7. Apr 28, 2019
  8. Apr 25, 2019
  9. Apr 24, 2019
  10. Apr 23, 2019
  11. Apr 25, 2019
  12. Apr 24, 2019
  13. Apr 23, 2019
  14. Apr 24, 2019
    • Yannick Tivisse's avatar
      [FIX] hr_holidays: Avoid erasing values on onchange if set · 4b0b00db
      Yannick Tivisse authored
      
      closes odoo/odoo#32790
      
      Signed-off-by: default avatarYannick Tivisse (yti) <yti@odoo.com>
      4b0b00db
    • Lucas Lefèvre's avatar
      [FIX] hr_holidays: Fix deleted default employee · 08da07b1
      Lucas Lefèvre authored
      The goal of commit 2dbce5e6 was to handle the company
      holiday type in onchange which was probably forgotten
      when the company type was introduced.
      However because the last `elif` was changed to `else`,
      the `else` clause is executed in some situations where
      it shouldn't.
      
      e.g. If holiday type is `employee` and an employee is set,
      the `else` clause is (obviously wrongly) executed.
      This is particularly a problem if the employee is not
      HR user nor manager. In that case, the field employee_id
      is invisible and its value has been deleted by the onchange.
      The allocation cannot be saved because it violates the
      sql constraint (employee is null).
      
      Also, the `mode_company_id` and `category_id` should be set
      to `False` when the holiday type is not company/category.
      08da07b1
    • Lucas Lefèvre's avatar
      [FIX] hr_holidays: Allow create department leave · d6242a34
      Lucas Lefèvre authored
      1. Open form view to create a leave
      2. Change the leave type to 'By department'
      3. Choose the department of the current user
      4. Save the leave
      5. Approve the leave
      => ValidationError, cannot have two leaves at the same time.
      
      In `@api.onchange('holiday_type')`, when choosing by department
      it sets `employee_id`, `mode_company_id` and `category_id`
      to `False` ONLY if the department is not already set.
      But by default, the employee is set to the user's employee
      and the department is set to the employee's department.
      Therefore the employee is never set to `False` and the
      department leave is linked to this employee.
      When validating the 'department' leave, an 'employee'
      leave is created for each employee in the department.
      For the current user, it crashes because the deparment leave overlaps with
      the 'employee' leave since the department leave is linked to
      the employee.
      d6242a34
    • Nicolas Martinelli's avatar
      [FIX] stock: add operation in mobile view · 17ac11d5
      Nicolas Martinelli authored
      
      Since it is possible to create an operation in the regular list view, it
      should also be possible to do it in the kanban mobile view.
      
      opw-1963527
      
      closes odoo/odoo#32907
      
      Signed-off-by: default avatarNicolas Martinelli (nim) <nim@odoo.com>
      17ac11d5
  15. Apr 23, 2019
Loading