Odoo/addons/calendar/views, branch 14.0 The current checkout of upstream Odoo [FIX] calendar: correct 'Date' filter behavior 2021-01-25T11:27:47+00:00 Nasreddin (bon) bon@odoo.com 2021-01-25T11:12:23+00:00 5f13ac8cf52c2042fe0b4697cbf41aa7f8714427 Issue - Install calendar - Go to calendar and set 'week' view - Go to first week of the year - Add a 'Full Day' event - Add an event of 'few hours' - Click on filters -> Date -> Q1 Only 'Full Day' events remains displayed. Cause 'start_date' is used to in the 'Date' filter and this field is set only on 'Full Day' events. Solution Use 'start' field instead since always set. opw-2439460 closes odoo/odoo#64992 Signed-off-by: bon-odoo <nboulif@users.noreply.github.com> 
Issue

	- Install calendar
	- Go to calendar and set 'week' view
	- Go to first week of the year
	- Add a 'Full Day' event
	- Add an event of 'few hours'
	- Click on filters -> Date -> Q1

	Only 'Full Day' events remains displayed.

Cause

	'start_date' is used to in the 'Date' filter
	and this field is set only on 'Full Day' events.

Solution

	Use 'start' field instead since always set.

opw-2439460

closes odoo/odoo#64992

Signed-off-by: bon-odoo <nboulif@users.noreply.github.com>
[FIX] calendar: Fix the 'my meetings' filter 2020-12-02T09:35:06+00:00 Urvi Soni uso@odoo.com 2020-11-26T12:58:42+00:00 03fc6e0276d93267efe0a23cf6209816188ce730 When we try 'My Meetings' filter in the Calendar module, it can't filter out the meetings that the user is attending. Steps to reproduce: go to calendar > list view > filters > my meetings Previously the filter was worked based on context `mymeetings` on search_read but during the refactoring of the calendar that is removed. So in this commit, add domain based on user_ids to filter the my meetings. closes odoo/odoo#62524 Taskid: 2389382 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com> 
When we try 'My Meetings' filter in the Calendar module,
it can't filter out the meetings that the user is attending.

Steps to reproduce:
go to calendar > list view > filters > my meetings

Previously the filter was worked based on context `mymeetings`
on search_read but during the refactoring of the calendar that
is removed.
So in this commit, add domain based on user_ids to filter the
my meetings.

closes odoo/odoo#62524

Taskid: 2389382
Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
[IMP] calendar: show more meeting details 2020-08-17T15:46:04+00:00 Yenthe666 yenthevg@gmail.com 2020-01-10T12:02:54+00:00 d249522d84700e0076c1b0342c0af6bf916234aa Before this commit there is no label shown at the top of the invite if the user hasn't done anything with the invite or if he chose 'Tentative'. Now it always shows the informative label. This commit also adds the description of a meeting subject as it can be interesting and important in many cases. closes odoo/odoo#43121 Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com> 
Before this commit there is no label shown at the top of the invite if
the user hasn't done anything with the invite or if he chose
'Tentative'. Now it always shows the informative label. This commit
also adds the description of a meeting subject as it can be
interesting and important in many cases.

closes odoo/odoo#43121

Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>
[FIX] website_calendar: remove privacy in search filter 2020-08-04T14:26:58+00:00 Jérémy Hennecart jeh@odoo.com 2020-07-03T14:45:17+00:00 1ea07e47fc334e186760aab4d8855e6576fd7439 Remove the field privacy in the search view since privacy is not considered as a public field. task-2285901 closes odoo/odoo#55398 X-original-commit: 0f6a531dcd7bba270ba83627d7140a76459c6d08 Related: odoo/enterprise#12193 Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com> 
Remove the field privacy in the search view since privacy
is not considered as a public field.

task-2285901

closes odoo/odoo#55398

X-original-commit: 0f6a531dcd7bba270ba83627d7140a76459c6d08
Related: odoo/enterprise#12193
Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>
[IMP] calendar: Use the avatar widget on event popover 2020-06-16T12:15:40+00:00 Bruno Boi boi@odoo.com 2020-05-27T09:06:31+00:00 fcf616c2e6e63e501dee9d76279b1f8185d8eacd The responsible of an event will now appear through the avatar widget. Taskid: 2263837 
The responsible of an event will now appear through the avatar widget.

Taskid: 2263837
 [REF] mail, *: refactor messaging with OWL 2020-06-15T18:12:21+00:00 Sébastien Theys seb@odoo.com 2020-06-15T18:12:21+00:00 3fea5b2136627c1d7e83b2a5e111952fe3eb10a1 This commit is a significant rewriting of client-side discuss, chatter, chat window, and messaging menu using OWL. The behavior should be broadly the same, with some slight functional changes here and there. From a technical standpoint, the code of messaging is mainly organized in 2 main groups of modules: - models, which are logical entities that depict the client-side state of messaging as a whole. - components, which are in charge of displaying information from models. This refactoring also introduces new JS guidelines regarding folder structure (/static) and naming rules for JS modules. Community PR: https://github.com/odoo/odoo/pull/39023 Enterprise PR: https://github.com/odoo/enterprise/pull/6249 Task-1914207 This PR is a collaborative work by Alexandre, Julien, Sébastien and Xavier, with the precious help of Lucas to speed it up towards the end. closes odoo/odoo#39023 Related: odoo/enterprise#6249 Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com> Co-authored-by: Alexandre Kühn <aku@odoo.com> Co-authored-by: Julien Giannone <jgi@odoo.com> Co-authored-by: Lucas Perais <lpe@odoo.com> Co-authored-by: Sébastien Theys <seb@odoo.com> Co-authored-by: Xavier Dubuc <xdu@odoo.com> 
This commit is a significant rewriting of client-side discuss, chatter,
chat window, and messaging menu using OWL. The behavior should be broadly
the same, with some slight functional changes here and there.

From a technical standpoint, the code of messaging is mainly organized in 2
main groups of modules:

- models, which are logical entities that depict the client-side state of
  messaging as a whole.
- components, which are in charge of displaying information from models.

This refactoring also introduces new JS guidelines regarding folder structure
(/static) and naming rules for JS modules.

Community PR: https://github.com/odoo/odoo/pull/39023
Enterprise PR: https://github.com/odoo/enterprise/pull/6249

Task-1914207

This PR is a collaborative work by Alexandre, Julien, Sébastien and Xavier,
with the precious help of Lucas to speed it up towards the end.

closes odoo/odoo#39023

Related: odoo/enterprise#6249
Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com>
Co-authored-by: Alexandre Kühn <aku@odoo.com>
Co-authored-by: Julien Giannone <jgi@odoo.com>
Co-authored-by: Lucas Perais <lpe@odoo.com>
Co-authored-by: Sébastien Theys <seb@odoo.com>
Co-authored-by: Xavier Dubuc <xdu@odoo.com>
[IMP] various: Add date filters on search views 2020-06-09T10:50:17+00:00 Yannick Tivisse yti@odoo.com 2020-06-04T07:34:58+00:00 893ec20236251f84dba117c709dd892645b78b9a PURPOSE ======= The task aims at adding date filters across various modules in preparation for the 'time range' feature rework on task 2245719 https://www.odoo.com/web#id=2245719&action=327&model=project.task&view_type=form&cids=1&menu_id=4720 SPECIFICATION ============= New date filters to compensate the deprecated time ranges feature: See task's pad for the complete details closes odoo/odoo#52398 Taskid: 2263661 Related: odoo/enterprise#10938 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com> 
PURPOSE
=======

The task aims at adding date filters across various modules in preparation
for the 'time range' feature rework on task 2245719

https://www.odoo.com/web#id=2245719&action=327&model=project.task&view_type=form&cids=1&menu_id=4720

SPECIFICATION
=============

New date filters to compensate the deprecated time ranges feature:

See task's pad for the complete details

closes odoo/odoo#52398

Taskid: 2263661
Related: odoo/enterprise#10938
Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
[IMP] project,...: Improve list views with new widgets 2020-05-25T12:44:14+00:00 Yannick Tivisse yti@odoo.com 2020-05-14T13:44:05+00:00 45f3659305359fff5b0c7bf3de7d49a25ba5c36d Purpose ======= Task 2195254 introduced many wonderful widgets to pimp the list view. This task aims at implemeting them into the Services apps: project, timesheets, helpdesk, expense, planning and field service. Remaining days: https://drive.google.com/file/d/1o4Wn47445GxLqBkw-ifH9MgtFU_437xz/view Avatar: https://drive.google.com/file/d/1yDwJWP0MZCUKZbqCa8hte1ziVTYRMMtb/view Activities: https://drive.google.com/file/d/1e_rXH50eZq4zY2HOzw7_pfgiD39SoRIl/view Field-specific decorations: https://drive.google.com/file/d/1WFnqJ-jkyDFftRHxWW4bgomoWrOpOuaY/view More control on buttons Specifications ============== You will find below a list of which widgets to apply to which fields by model. Some changes have to be done in the form/kanban views as well. 1) project.task remaining days -> date_deadline -> list + kanban + form views hide this field if is_closed is true avatar -> user_id -> list view activities -> 'next activity' field to be added -> list view field-specific decorations https://nimb.ws/ACewrY remove the current orange/red decorations we have if planned_hours > 0, display the remaining_hours field in (list view): red if progress is > 100% orange if progress is between 80% and 100% green if progress is <80% display unit_amount in red if > 24:00 -> form view 2) rating.rating display the rating in: green = satisfied orange = not_satisfied red = highly_dissatisfied list + form views 3) project.project avatar -> user_id -> list + form views 4) account.analytic.line avatar -> employee_id -> list view display unit_amount in red if > 24:00 -> list + kanban + form view https://nimb.ws/eIWa7E merge the timer and duration fields together 5) helpdesk.ticket avatar user_id -> list view employee_id under timesheet_ids -> form view remaining hours -> sla_deadline activities -> 'next activity' field to be added -> list view field specific decoration -> display unit_amount in red if > 24:00 -> form view 6) hr.expense avatar -> employee_id -> list view activities -> 'next activity' field to be added -> list view badge -> state -> list view draft = blue reported = green approved = green done = green refused = red combine the unit_amount and the currency_id fields (see the total_amount field for reference) -> list view (idem for the expense_line_ids one2many on hr.expense.sheet) display the total_amount in bold move 'company_id' before 'amount' 7) hr.expense.sheet avatar employee_id -> list view user_id -> list view activities -> 'next activity' field to be added -> list view badge -> state -> list view draft = blue submit = green approve = green post = green done = green cancel = red display the total_amount in bold move 'company_id' before 'amount' 8) planning.slot avatar -> employee_id -> list view decoration display the allocated_percentage field in red if > 100% -> list + form view display the forecast_hours field in red if > planned hours and if planned_hours > 0 -> form view display the effective_hours field in red if > forecast_hours and if forecast_hours > 0 -> form view 9) misc calendar.event -> avatar -> user_id -> form view mail.activity.type -> combine the delay_count and delay_unit fields together -> list view note.note -> 'next activity' field to be added -> list view crm.lead.mining.request combine the lead_number and lead_type fields together -> list view display the name in bold badge -> state draft = blue done = green error = red planning.slot.template -> display the duration field in red if it is = 0 closes odoo/odoo#51271 Taskid: 2248351 Related: odoo/enterprise#10605 Related: odoo/upgrade#1252 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com> 
Purpose
=======

Task 2195254 introduced many wonderful widgets to pimp the list view.
This task aims at implemeting them into the Services apps: project,
timesheets, helpdesk, expense, planning and field service.

Remaining days: https://drive.google.com/file/d/1o4Wn47445GxLqBkw-ifH9MgtFU_437xz/view
Avatar: https://drive.google.com/file/d/1yDwJWP0MZCUKZbqCa8hte1ziVTYRMMtb/view
Activities: https://drive.google.com/file/d/1e_rXH50eZq4zY2HOzw7_pfgiD39SoRIl/view
Field-specific decorations: https://drive.google.com/file/d/1WFnqJ-jkyDFftRHxWW4bgomoWrOpOuaY/view
More control on buttons

Specifications
==============

You will find below a list of which widgets to apply to which fields by
model. Some changes have to be done in the form/kanban views as well.

1) project.task

remaining days -> date_deadline -> list + kanban + form views
hide this field if is_closed is true
avatar -> user_id -> list view
activities -> 'next activity' field to be added -> list view
field-specific decorations
https://nimb.ws/ACewrY remove the current orange/red decorations we have
if planned_hours > 0, display the remaining_hours field in (list view):
red if progress is > 100%
orange if progress is between 80% and 100%
green if progress is <80%
display unit_amount in red if > 24:00 -> form view

2) rating.rating

display the rating in:
green = satisfied
orange = not_satisfied
red = highly_dissatisfied
list + form views

3) project.project

avatar -> user_id -> list + form views

4) account.analytic.line

avatar -> employee_id -> list view
display unit_amount in red if > 24:00 -> list + kanban + form view
https://nimb.ws/eIWa7E merge the timer and duration fields together

5) helpdesk.ticket

avatar
user_id -> list view
employee_id under timesheet_ids -> form view
remaining hours -> sla_deadline
activities -> 'next activity' field to be added -> list view
field specific decoration -> display unit_amount in red if > 24:00 -> form view

6) hr.expense

avatar -> employee_id -> list view
activities -> 'next activity' field to be added -> list view
badge -> state -> list view
draft = blue
reported = green
approved = green
done = green
refused = red
combine the unit_amount and the currency_id fields (see the total_amount field for reference) -> list view (idem for the expense_line_ids one2many on hr.expense.sheet)
display the total_amount in bold
move 'company_id' before 'amount'

7) hr.expense.sheet

avatar
employee_id -> list view
user_id -> list view
activities -> 'next activity' field to be added -> list view
badge -> state -> list view
draft = blue
submit = green
approve = green
post = green
done = green
cancel = red
display the total_amount in bold
move 'company_id' before 'amount'

8) planning.slot

avatar -> employee_id -> list view
decoration
display the allocated_percentage field in red if > 100% -> list + form view
display the forecast_hours field in red if > planned hours and if planned_hours > 0 -> form view
display the effective_hours field in red if > forecast_hours and if forecast_hours > 0 -> form view

9) misc

calendar.event -> avatar -> user_id -> form view
mail.activity.type -> combine the delay_count and delay_unit fields together -> list view
note.note -> 'next activity' field to be added -> list view
crm.lead.mining.request
combine the lead_number and lead_type fields together -> list view
display the name in bold
badge -> state
draft = blue
done = green
error = red
planning.slot.template -> display the duration field in red if it is = 0

closes odoo/odoo#51271

Taskid: 2248351
Related: odoo/enterprise#10605
Related: odoo/upgrade#1252
Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
[IMP] various: Update list views with new widgets 2020-05-15T08:24:05+00:00 Yannick Tivisse yti@odoo.com 2020-05-15T08:09:20+00:00 7b714a3bc727614c11ce1fc64f971f53f6db3137 Purpose ======= The following task implemented new widgets/features in the listview for better UI. https://www.odoo.com/web#id=2195254&action=327&model=project.task&view_type=form&cids=1&menu_id=4720 The goal of the current task is to use those to upgrade our listviews Specification ============= Below are change requests on various listviews. Remove decoration-bf="message_needaction==True" from every listview in every module. PRODUCT - stock.view_stock_product_template_tree (product template) remove all decorations from <tree> set the following decorations on 'virtual_available' and 'qty_available' decoration-danger="virtual_available&lt;0" decoration-warning="virtual_available==0" also set decoration-bf on 'virtual_available' apply the same modifications on stock.view_stock_product_tree for product variants SUBSCRIPTION - sale_subscription.sale_subscription_view_list remove all decorations from <tree> 'stage_id' field set <field name="stage_id" widget="badge" decoration-info="stage_category == 'draft'" decoration-success="stage_category == 'progress'"/> 'recurring_next_date' field set <field name="recurring_next_date" string="Next Invoice" widget="remaining_days" attrs="{'invisible': [('stage_category', '!=', 'progress')]}"/> set decoration-bf on 'code' and 'recurring_total_incl' move 'percentage_satisfaction' before 'recurring_total_incl' set widget="many2one_avatar_user" on 'user_id' add <field name="activity_ids" widget="list_activity"/> after 'user_id' ELEARNING - website_slides.slide_channel_view_tree set widget="many2one_avatar_user" on 'user_id' 'enroll' field set <field name="enroll" widget="badge" decoration-success="enroll == 'public'" decoration-info="enroll == 'invite'" decoration-warning="enroll == 'payment'"/> POS - point_of_sale.view_pos_order_tree remove all decorations from <tree> 'state' field make visible and move it at the end of the view set <field name="state" widget="badge" decoration-info="state == 'draft'" decoration-success="state not in ('draft','cancel')"/> set decoration-bf on 'name' APPRAISAL - hr_appraisal.view_hr_appraisal_tree 'state' field set <field name="state" widget="badge" decoration-info="state in ('new','pending')" decoration-success="state == 'done'"/> 'date_close' field set <field name="date_close" widget="remaining_days" attrs="{'invisible': ['|',('state','=','done'),('state','=','cancel')]}"/> PAYMENT - account.view_account_payment_tree remove all decorations from <tree> 'state' field set <field name="state" widget="badge" decoration-info="state == 'draft'" decoration-success="state == 'posted'"/> move 'company_id' before 'amount' CONTRACT - hr_contract.hr_contract_view_tree remove all decorations from <tree> 'state' field set <field name="state" widget="badge" decoration-info="state == 'draft'" decoration-warning="state == 'close'" decoration-success="state == 'open'"/> set widget="many2one_avatar_employee" on 'employee_id' PAYSLIPS - hr_payroll.view_hr_payslip_tree remove all decorations from <tree> 'state' field set <field name="state" widget="badge" decoration-info="state == 'draft'" decoration-warning="state == 'verify'" decoration-success="state in ('done','paid')"/> set decoration-bf on 'number' and 'net_wage' move 'company_id' before 'basic_wage' set widget="many2one_avatar_employee" on 'employee_id' SURVEY - survey.survey_tree 'state' field set <field name="state" widget="badge" decoration-info="state == 'draft'" decoration-success="state == 'open'"/> APPLICATION - hr_recruitment.crm_case_tree_view_job set widget="date' on 'create_date' set widget="priority' on 'priority' set widget="many2one_avatar_user" on 'user_id' TIME OFF - hr_holidays.hr_leave_view_tree remove all decorations from <tree> 'state' field set <field name="state" widget="badge" decoration-info="state == 'draft'" decoration-warning="state in ('confirm','validate1')" decoration-success="state == 'validate'"/> apply the same changes in hr_holidays.hr_leave_allocation_view_tree closes odoo/odoo#51305 Taskid: 2256589 Related: odoo/enterprise#10614 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com> 
Purpose
=======

The following task implemented new widgets/features in the listview for better UI.
https://www.odoo.com/web#id=2195254&action=327&model=project.task&view_type=form&cids=1&menu_id=4720

The goal of the current task is to use those to upgrade our listviews

Specification
=============

Below are change requests on various listviews.

Remove decoration-bf="message_needaction==True" from every listview in every module.

PRODUCT - stock.view_stock_product_template_tree (product template)

remove all decorations from <tree>
set the following decorations on 'virtual_available' and 'qty_available'
decoration-danger="virtual_available&lt;0"
decoration-warning="virtual_available==0"
also set decoration-bf on 'virtual_available'
apply the same modifications on stock.view_stock_product_tree for product variants

SUBSCRIPTION - sale_subscription.sale_subscription_view_list

remove all decorations from <tree>
'stage_id' field
set <field name="stage_id" widget="badge" decoration-info="stage_category == 'draft'" decoration-success="stage_category == 'progress'"/>
'recurring_next_date' field
set <field name="recurring_next_date" string="Next Invoice" widget="remaining_days" attrs="{'invisible': [('stage_category', '!=', 'progress')]}"/>
set decoration-bf on 'code' and 'recurring_total_incl'
move 'percentage_satisfaction' before 'recurring_total_incl'
set widget="many2one_avatar_user" on 'user_id'
add <field name="activity_ids" widget="list_activity"/> after 'user_id'

ELEARNING - website_slides.slide_channel_view_tree

set widget="many2one_avatar_user" on 'user_id'
'enroll' field
set <field name="enroll" widget="badge" decoration-success="enroll == 'public'" decoration-info="enroll == 'invite'" decoration-warning="enroll == 'payment'"/>

POS - point_of_sale.view_pos_order_tree

remove all decorations from <tree>
'state' field
make visible and move it at the end of the view
set <field name="state" widget="badge" decoration-info="state == 'draft'" decoration-success="state not in ('draft','cancel')"/>
set decoration-bf on 'name'

APPRAISAL - hr_appraisal.view_hr_appraisal_tree

'state' field
set <field name="state" widget="badge" decoration-info="state in ('new','pending')" decoration-success="state == 'done'"/>
'date_close' field
set <field name="date_close" widget="remaining_days" attrs="{'invisible': ['|',('state','=','done'),('state','=','cancel')]}"/>

PAYMENT - account.view_account_payment_tree

remove all decorations from <tree>
'state' field
set <field name="state" widget="badge" decoration-info="state == 'draft'" decoration-success="state == 'posted'"/>
move 'company_id' before 'amount'

CONTRACT - hr_contract.hr_contract_view_tree

remove all decorations from <tree>
'state' field
set <field name="state" widget="badge" decoration-info="state == 'draft'" decoration-warning="state == 'close'" decoration-success="state == 'open'"/>
set widget="many2one_avatar_employee" on 'employee_id'

PAYSLIPS - hr_payroll.view_hr_payslip_tree

remove all decorations from <tree>
'state' field
set <field name="state" widget="badge" decoration-info="state == 'draft'" decoration-warning="state == 'verify'" decoration-success="state in ('done','paid')"/>
set decoration-bf on 'number' and 'net_wage'
move 'company_id' before 'basic_wage'
set widget="many2one_avatar_employee" on 'employee_id'

SURVEY - survey.survey_tree

'state' field
set <field name="state" widget="badge" decoration-info="state == 'draft'" decoration-success="state == 'open'"/>

APPLICATION - hr_recruitment.crm_case_tree_view_job

set widget="date' on 'create_date'
set widget="priority' on 'priority'
set widget="many2one_avatar_user" on 'user_id'

TIME OFF - hr_holidays.hr_leave_view_tree

remove all decorations from <tree>
'state' field
set <field name="state" widget="badge" decoration-info="state == 'draft'" decoration-warning="state in ('confirm','validate1')" decoration-success="state == 'validate'"/>
apply the same changes in hr_holidays.hr_leave_allocation_view_tree

closes odoo/odoo#51305

Taskid: 2256589
Related: odoo/enterprise#10614
Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
[REF] calendar: Move renderer in its own file 2020-04-09T08:59:34+00:00 Lucas Lefèvre lul@odoo.com 2020-04-06T16:06:19+00:00 39aef65f37a8ae969527b31a680eb27fddbc5710