Skip to content
Snippets Groups Projects
  1. Nov 07, 2019
  2. Oct 30, 2019
  3. Nov 06, 2019
  4. Nov 07, 2019
    • jvm-odoo's avatar
      [FIX] crm: fix lead/opportunity meeting scheduling · a2c7e6e3
      jvm-odoo authored
      
      Reproduce the issue:
       - In the CRM app, create a lead/opportunity.
       - Schedule a meeting for this opportunity via
         the chatter and click on create.
       - Go back, the "Meeting" stat button is now at 1
       - Schedule a meeting for this opportunity via
         the chatter and click on edit then create.
       - Go back, the "Meeting" stat button is still at 1
      
      Cause:
      When we click directly on create, the opportunity ID is in the defaults
      option but when we click on edit, there is no opportunity ID.
      
      So, this commit use the context to retrieve the concerned opportunity
      and set it if it is not already set.
      
      I splitted the solution into a private method for a better readability.
      
      OPW-2092920
      
      closes odoo/odoo#39952
      
      X-original-commit: 59d154dc
      Signed-off-by: default avatarJason Van Malder <jasonvanmalder@users.noreply.github.com>
      a2c7e6e3
    • fw-bot's avatar
      [FIX] hr: make hr.job visible without recruitment · e4de2b2e
      fw-bot authored
      
      Without hr_recruitment it was not possible to import/export the hr.job
      as they were not visible.
      
      closes #22069
      
      closes odoo/odoo#39914
      
      Taskid: 2088277
      Signed-off-by: default avatarYannick Tivisse (yti) <yti@odoo.com>
      e4de2b2e
  5. Nov 06, 2019
  6. Oct 30, 2019
  7. Nov 06, 2019
  8. Nov 05, 2019
  9. Nov 04, 2019
    • jvm-odoo's avatar
      [FIX] account: fix mass mail wizard · 2496125f
      jvm-odoo authored
      - In the sales or accounting module, create some invoices.
      - Select them then click on `action > send & print`
      - The wizard opens but not in the mass mail mode.
      
      It creates some inconsistency and if you click on send,
      the invoices are sent to the wrong customer.
      
      Sometimes, the invoices are not sent at all.
      
      I think the problem comes from the `_compute_composition_mode` method
      who set the value of `composition_mode` on the wizard instead of
      on the composer.
      
      OPW-2085837
      2496125f
  10. Nov 06, 2019
  11. Nov 04, 2019
  12. Nov 06, 2019
  13. Nov 05, 2019
  14. Oct 30, 2019
    • Christophe Monniez's avatar
      [FIX] packaging: compute winpython path with package.py args · ac90d858
      Christophe Monniez authored
      
      When building the MS Windows package, the PYTHON_VERSION variable is not
      used and the WinPython path is hard coded in the Makefile and NSI file.
      This prevent the usage of a newer version of Python.
      
      With this commit, the PYTHON_VERSION is used to compute the WinPython
      Python directory. That way, this directory can be derived from
      package.py command line argument --vm-winxp-python-version.
      
      Also the less windows binaries are not packaged anymore.
      
      closes odoo/odoo#39816
      
      Signed-off-by: default avatarChristophe Monniez (moc) <moc@odoo.com>
      ac90d858
  15. Nov 05, 2019
    • jvm-odoo's avatar
      [FIX] project: fix multi level subtask · 41173789
      jvm-odoo authored
      
      - Create a project
      - Create 3 tasks in the project (top, middle, bottom)
      - Set top as the parent of middle
      - Set middle as the parent of bottom
      
      We don't want to allow multi level subtasks. The behavior is not the
      same if you set middle as the parent of bottom first. The "parent task"
      field will not be displayed.
      
      This commit remove the tasks who have a parent from the m2o field.
      
      OPW-2087921
      
      closes odoo/odoo#39805
      
      X-original-commit: c7966b64
      Signed-off-by: default avatarJason Van Malder <jasonvanmalder@users.noreply.github.com>
      41173789
    • wan's avatar
      [FIX] account: payment reference exact match without spaces · 9b5d1f6b
      wan authored
      
      The spaces should not be important in a structured reference.
      Also, we should not have to include the second batch as that batch
      (previously the first) was intended to match the payment reference.
      By including it, we may have too much false positives proposed in the
      widget and even worse: auto reconciled.
      
      closes odoo/odoo#39334
      
      Signed-off-by: default avatarQuentin De Paoli (qdp) <qdp@openerp.com>
      9b5d1f6b
  16. Oct 31, 2019
    • wan's avatar
      [FIX] account: match on sanitized bank number · 733ca62a
      wan authored
      FIX 2092459
      The reconciliation tries to find partner based on the bank number, but
      that bank number may not be encoded the same way depending where the
      statement lines come from.
      A solution is to sanitize the bank number at query time.
      733ca62a
  17. Nov 05, 2019
    • Adrian Torres's avatar
      [FIX] base: avoid triggering recomputation when deleted selection · 0ccf2ab8
      Adrian Torres authored
      
      In 6b048a8b most issue with trigger causing error when uninstalling a
      module were solved.
      
      But there was a particular case if the current uninstallation of modules
      there was an update of `ir.model.fields.selection` to be removed. The
      unlink of `ir.model.fields.selection` would cause a `setup_models` call
      that would add all removed triggers back and possibly down the line
      cause an trigger recomputation error.
      
      With this changeset, we do as is already done for ir.model.fields and do
      not re-initialize the registry during module uninstallation.
      
      opw-2098915
      closes #39796
      
      Signed-off-by: default avatarAdrian Torres (adt) <adt@odoo.com>
      0ccf2ab8
Loading