Skip to content
Snippets Groups Projects
  1. Mar 04, 2021
  2. Mar 01, 2021
  3. Mar 03, 2021
  4. Mar 04, 2021
  5. Mar 02, 2021
  6. Mar 04, 2021
    • Odoo's Mergebot's avatar
      [MERGE] web,hr_timesheet,partner_autocomplete: make multi company timesheet uom work · f11fcba8
      Odoo's Mergebot authored
      
      # Purpose
      
      This PR's primary objective is to ensure that the timesheet uom is working in accordance with the company settings in a multi company environment.
      
      Prior to this PR:
      
       - The timesheet preferences sent to the front end were always those of the default
         company of the user.
       - The timesheet related widgets initialisation process (adding the correct ones in
         the fieldRegistry) was performed before the front end treatment of cids and coockies
         which prevented applying the front end selected company settings.
      
      After this PR:
      
       - A dictionnary is used in the session in order to structure the companies info.
       - The company timesheet preferences are sent to the front end through the company dict.
       - The uom info is sent to the front end through the session.
       - The timesheet uom is now managed from the frontend and is now in sync with the settings.
       - Timesheet widgets are initialised during the AbstractWebClient init and are in sync with
         the multicompany front end settings
      
      task-2168337
      
      --
      I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
      
      closes odoo/odoo#66551
      
      Signed-off-by: default avatarYannick Tivisse (yti) <yti@odoo.com>
      Unverified
      f11fcba8
    • Odoo's Mergebot's avatar
      [MERGE] mail, mass_mailing, event, various: improve usability across various... · 667d3d11
      Odoo's Mergebot authored
      [MERGE] mail, mass_mailing, event, various: improve usability across various marketing-related apps (activities, marketing)
      
      # Purpose
      General Marketing usability improvements based on what has been seen observing users on Fullstory.
      As the changes are relatively minor and related to specific apps, the rationale and improvements will be explained in more details in each commit.
      # Commits
      ##### [IMP] `base`: modify some displayed texts for res_partner
      * Error messages when trying to delete/archive a partner linked to an active user
      * Partner Form placeholders
      * Update main_flow tour to be consistent with above changes
      * Update test_orm to use a model with less functional constraints
      ##### [IMP] `mass_mailing_sms`: prevent raising an error in sms mailing
      * Allow to launch a sms campaign without recipients without raising an error
      ##### [IMP] `mass_mailing`: add various usability improvements
      * Mass mailing preview in a new tab (to prevent data loss when leaving the page)
      * Data display adjustments (better wording...)
      ##### [IMP] `mail`: revamp the activity type form view
      * Change "force_next" checkbox into "chaining_type" selection
      * Update the Form layout and wording
      * Renamed fields :
        * default_next_type_id -> triggered_next_type_id
        * next_type_ids -> suggested_next_type_ids
        * default_description -> default_note
      ##### [IMP] `event`: improve the event form editor and update the tour
      * Fix an undesired behavior with duplicate lines when switching event_type templates
      * Remove steps from the event tour
      ##### [IMP] `web`: add an initial_date context key for CalendarView
      * Add a context key ('initial_date') to the calendar view (to open it around a specified date)
      ##### [IMP] `crm`: add a reschedule action for activities
      * Add a reschedule action alongside snooze 7d, for event-related activities
      ##### [IMP] `crm`: change the search order for a won stage
      * In case "not won" stages are placed between "won" stages, put an opportunity marked as "won" in the correct stage (higher sequence if possible)
      ##### [MOV] `website_event`: move the website_event tour to tests/tours
      * The scope of another tour (event_tour) include the scope of this tour and actually starts from the Event module. This smaller tour is thus disabled and kept as a test.
      # Links
      Task ID : 2410217
      ENT PR : https://github.com/odoo/enterprise/pull/15406
      UPGRADE PR : https://github.com/odoo/upgrade/pull/2167
      
      
      
      closes odoo/odoo#63370
      
      Related: odoo/upgrade#2167
      Related: odoo/enterprise#15406
      Signed-off-by: default avatarThibault Delavallee (tde) <tde@openerp.com>
      Unverified
      667d3d11
    • Laurent Stukkens (LTU)'s avatar
      [IMP] hr_timesheet: add js tests for timesheet_uom · a77aad88
      Laurent Stukkens (LTU) authored
      Prior to this commit:
      
      - There were no tests on the timesheet_uom and the fact that the widget
        that is loaded in the fieldRegistry is corresponding to the current
        company preferences.
      
      After this commit:
      
      - Tests will be performed in order to check that the timesheet_uom that
        is loaded in the fieldRegistry is corresponding to the current company
        preferences.
      
      task-2168337
      Closes: #66551
      a77aad88
    • Laurent Stukkens (LTU)'s avatar
      [FIX] web,hr_timesheet,partner_autocomplete: make multi company timesheet uom work · 3e847fc8
      Laurent Stukkens (LTU) authored
      This commit's primary objective is to ensure that the timesheet uom is working in accordance
      with the company settings in a multi company environment.
      
      Prior to this commit:
      
       - The timesheet preferences sent to the front end were always those of the default
         company of the user.
       - The timesheet related widgets initialisation process (adding the correct ones in
         the fieldRegistry) was performed before the front end treatment of cids and coockies
         which prevented applying the front end selected company settings.
      
      After this commit:
      
       - A dictionnary is used in the session in order to structure the companies info.
       - The company timesheet preferences are sent to the front end through the company dict.
       - The uom info is sent to the front end through the session.
       - The timesheet uom is now managed from the frontend and is now in sync with the settings.
       - Timesheet widgets are initialised during the AbstractWebClient init and are in sync with
         the multicompany front end settings
      
      task-2168337
      Closes: #66551
      3e847fc8
    • Laurent Stukkens (LTU)'s avatar
      [FIX] web: add missing semicolons and typo in multi company files · c815ba7d
      Laurent Stukkens (LTU) authored
      Before this commit:
      
       - Some semicolon where missing
       - There was a typo in the variable name
      
      After this commit:
      
       - The above problems are solved
      
      task-2168337
      Closes: #66551
      c815ba7d
  7. Mar 03, 2021
  8. Mar 04, 2021
    • Odoo's Mergebot's avatar
      [MERGE] sales_team, crm, crm_iap_*: improve reporting usability · 03e2bd96
      Odoo's Mergebot authored
      
      PURPOSE
      
      Purpose of this merge is to improve reporting usability
      and views in crm, lead generation and iap services.
      
      SPECIFICATIONS
      
      Some usability improvements going to be done by this merge are listed
      below.
      
      Improve the action helpers for the actions bound to below listed menus
      for better usability:
      
        * My Activities
        * Leads
        * Leads Analysis
      
      Along with that, this commit also improves the following:
      
        * while generating leads, make 'Industries' field required on the modal so
          that results obtained are actionable instead of random leads;
        * after trying to generate leads, if no result is found, the same pop-up
          opens again with same criteria and displays a waring in the pop-up. It
          informs users that leads are not found and no credits are spent for their
          last search;
        * improve the warning message for unsuccessful enrichment due to invalid
          email;
      
      This merge adds the color_picker widget for setting valid color of
      CRM tags in the form view.
      
      With this merge, the 'Enrich' button on lead now appears only after the
      email is set and valid, which previously appeared even if no email is set
      or if the value is not a valid email.
      
      Right now, for the fetched contacts through enrichment, we display
      name and title in separate columns (in the chatter), that leaves
      lesser space for email and phone.
      
      With this commit, we merge name and title columns, and provide a bit
      extra space to email and phone so that chances for them being wrapped
      in a new line are less. Also, if phone number is not available in any
      contacts, the 'Phone' column is hidden, giving even more space for the
      Name/Title and Email columns.
      
      LINKS
      
      COM PR odoo/odoo#64075
      ENT PR odoo/enterprise#15561
      Task ID-2393253
      
      Signed-off-by: default avatarThibault Delavallee (tde) <tde@openerp.com>
      Unverified
      03e2bd96
  9. Mar 03, 2021
    • Géry Debongnie's avatar
      [FIX] web: prevent traceback when pressing TAB in color_picker widget · 2c777546
      Géry Debongnie authored
      
      The color_picker widget, that can be seen for example in the track form
      view for event tracks, had an issue: if the user clicked on it, then
      pressed TAB, a traceback was displayed.
      
      The problem comes from the fact that the color picker widget inherits
      from FieldInput, but is not a fieldinput, so many expectations made by
      the FieldInput code do not hold, such as the code run when handling
      navigation (by TAB and such keypress). Because of that, the code in
      _onNavigationMove crashed, because it expected an input.
      
      Since this is a bug fix, I simply disabled the navigation in that case,
      so no crash happens.  Sadly, this widget has still a big issue: it
      clearly does not work as most users would expect: pressing TAB or arrows
      should update the selection.  But this would be a more complicated
      refactoring, for a bug which is clearly not critical, therefore this
      commit implements the simple and safe solution.
      
      Also, we disable the focus outline to minimize the wrong expectation.
      Seeing them kind of implied that one could update the selection with the
      keyboard.
      
      Note that the widget color_picker was moved from another addon to web/, without
      any tests nor documentation.
      
      OPW 2467369
      
      closes odoo/odoo#67195
      
      X-original-commit: 580456b6
      Signed-off-by: default avatarAaron Bohy (aab) <aab@odoo.com>
      2c777546
    • ijas ahammed's avatar
      [IMP] crm_iap_lead: merge name and title in enrichment template · 6832d7f3
      ijas ahammed authored
      Right now, for the fetched contacts through enrichment, we display
      name and title in separate columns (in the chatter), that leaves
      lesser space for email and phone.
      
      With this commit, we merge name and title columns, and provide a bit
      extra space to email and phone so that chances for them being wrapped
      in a new line are less. Also, if phone number is not available in any
      contacts, the 'Phone' column is hidden, giving even more space for the
      Name/Title and Email columns.
      
      Task ID-2393253
      COM PR odoo/odoo#64075
      6832d7f3
    • ijas ahammed's avatar
      [FIX] crm_iap_lead_enrich: show 'Enrich' button only if email is valid · da523d20
      ijas ahammed authored
      With this commit, the 'Enrich' button on lead now appears only after the
      email is set and valid, which previously appeared even if no email is set
      or if the value is not a valid email.
      
      Task ID-2393253
      COM PR odoo/odoo#64075
      da523d20
    • ijas ahammed's avatar
      [IMP] sales_team: add color_picker widget for CRM tags · 52c37235
      ijas ahammed authored
      This commit adds the color_picker widget for setting valid color of
      CRM tags in the form view.
      
      Task ID-2393253
      COM PR odoo/odoo#64075
      52c37235
    • ijas ahammed's avatar
      [IMP] sales_team, crm{_iap}*: improve action helpers and usability · 79476eb3
      ijas ahammed authored
      This commit improves the action helpers for the actions bound to below listed
      menus for better usability:
      
        * My Activities
        * Leads
        * Leads Analysis
      
      Along with that, this commit also improves the following:
      
        * while generating leads, make 'Industries' field required on the modal so
          that results obtained are actionable instead of random leads;
        * after trying to generate leads, if no result is found, the same pop-up
          opens again with same criteria and displays a waring in the pop-up. It
          informs users that leads are not found and no credits are spent for their
          last search;
        * improve the warning message for unsuccessful enrichment due to invalid
          email;
      
      COM PR odoo/odoo#64075
      ENT PR odoo/enterprise#15561
      Task ID-2393253
      79476eb3
    • Laurent Smet's avatar
      [FIX] hr_expense: Don't write 'payment_id' on aml · bb839c75
      Laurent Smet authored
      
      This line was an hack to manage the custom register payment wizard of hr_expense.
      Since this wizard is gone and 'payment_id' is a related stored field in account.move.line, we should not write such data explicitely.
      
      closes odoo/odoo#67162
      
      X-original-commit: 2d7f45e7
      Signed-off-by: default avataroco-odoo <oco-odoo@users.noreply.github.com>
      bb839c75
    • Odoo's Mergebot's avatar
      [MERGE] survey: improve certification templates · 212b107f
      Odoo's Mergebot authored
      
      PURPOSE
      
      Improve certification templates and make them more aligned with current
      state of the art certifications.
      
      SPECIFICATIONS
      
      Design has been completely redone to be more modern.
      
      Also displays dynamic certification number based on the ID of
      certification record for both modern and classic layouts. It consists in
      minimum 10 digits. It means that if the ID of the record is 5 it is displayed
      as 0000000005.
      
      Also improves the behavior by adding name of the certification in page title
      so that use can see the proper string on browser tab. For doing so, we create
      a new wrapper template that sets the title for the page, and use an iframe
      to loads the pdf file from existing controlloer (which returns response for the
      preview pdf).
      
      LINKS
      
      Task ID-2341847
      COM PR #66028
      
      Signed-off-by: default avatarThibault Delavallee (tde) <tde@openerp.com>
      Unverified
      212b107f
    • Lavish Chhatwani's avatar
      [IMP] survey: display title on certification preview · 45eb2b39
      Lavish Chhatwani authored
      Right now while previewing the certification template, the proper title is not
      displayed on the tab of browsers.
      
      This commit improves the behavior by adding name of the certification in title
      so that use can see the proper string on browser tab. For doing so, we create
      a new wrapper template that sets the title for the page, and use an iframe
      to loads the pdf file from existing controlloer (which returns response for the
      preview pdf).
      
      Task ID-2341847
      COM PR odoo/odoo#66028
      45eb2b39
    • Dharmraj Jhala's avatar
      [IMP] survey: display certification number based on ID · 45b448af
      Dharmraj Jhala authored
      This commit displays dynamic certification number based on the ID of
      certification record for both modern and classic layouts. It consists in
      minimum 10 digits. It means that if the ID of the record is 5 it is displayed
      as 0000000005.
      
      Task ID-2341847
      COM PR odoo/odoo#66028
      45b448af
    • Elisabeth Dickinson's avatar
      [REF] survey: implement new certificate templates · ae4435af
      Elisabeth Dickinson authored
      
      Improve certification templates and make them more aligned with current
      state of the art certifications.
      
      Task ID-2341847
      COM PR odoo/odoo#66028
      
      Co-Authored-By: default avatarElisabeth Dickinson <edi@odoo.com>
      Co-Authored-By: default avatarDharmrajsinh Jhala <dja@odoo.com>
      ae4435af
    • Julien Castiaux's avatar
      [FIX] mass_mailing: wrong clicks_ratio compute · 412973f7
      Julien Castiaux authored
      
      Fine tuning of 2d63fff1
      
      closes odoo/odoo#67173
      
      X-original-commit: d4210430
      Signed-off-by: default avatarJulien Castiaux <Julien00859@users.noreply.github.com>
      412973f7
    • Géry Debongnie's avatar
      [FIX] web: issue with field named "length" · 0cf7b8fd
      Géry Debongnie authored
      
      The underscore (_) library has a bug in which the _.each method does not
      work with object which contains a "length" property. This is because it
      does look for that key and if it is a number, it will assume that it is
      an array with that length value.  Nicely done...
      
      If that length value is set to 0, then it will just do nothing, since it
      thinks that it is dealing with an empty array.
      
      Note that if the value is set to an object, _.each is smart enough to
      notice that it cannot be an array, and will do the correct thing in this
      case.
      
      Usually, our _.each calls are safe, since we usually iterate on arrays,
      or on object with safe keys, or on object with values that cannot be a
      number.
      
      But there was 2 unsafe calls in basic_model, which leads to strange
      bugs: some code is skipped, and the form view is then confused.  The
      motivation for this fix is the fact that onchanges are not applied at
      all, if there is a length field set to 0.
      
      To fix this, we can just avoid using _.each.  Note to every Odoo JS
      developers reading this: new Odoo code should avoid using the _ and $
      libraries, because we do not really need them, and we want to keep our
      dependencies to the strict mininum.
      
      OPW: #2465808
      closes odoo/odoo#66126
      
      closes odoo/odoo#67172
      
      X-original-commit: 8dbd1efe
      Signed-off-by: default avatarAaron Bohy (aab) <aab@odoo.com>
      Signed-off-by: default avatarGéry Debongnie (ged) <ged@openerp.com>
      0cf7b8fd
    • Damien Abeloos's avatar
      [MOV] website_event: move the website_event tour to tests/tours · 72fab547
      Damien Abeloos authored
      * Reassign the "event" tour to a classic test
        - Only the "event_tour" that starts from the Event App should be kept from a
          user perspective.
        - The "event" tour that launched itself once upon installing the Event App
          from the Website (Website App) and only covered the front-end part of
          the event creation will now only be kept as a classic test tour.
        - This tour is renamed "website_event_tour" instead of "event" for
          disambiguity with the other tour called "event_tour"
      
      * This tour is now only intended to be used as a test, and as such, is moved
        to `tests/tours`
      
      Task ID : 2410217
      PR : #63370
      72fab547
Loading