<feed xmlns='http://www.w3.org/2005/Atom'>
<title>Odoo/addons/timer/security, branch 14.0</title>
<subtitle>The current checkout of upstream Odoo</subtitle>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/'/>
<entry>
<title>[MOV] timer: Move to Enterprise</title>
<updated>2020-06-15T13:51:20+00:00</updated>
<author>
<name>jbm-odoo</name>
<email>jbm@odoo.com</email>
</author>
<published>2020-06-05T15:13:53+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=d6a23144d5c5b85c2a02097bcbb3e006a9c2c52a'/>
<id>d6a23144d5c5b85c2a02097bcbb3e006a9c2c52a</id>
<content type='text'>
taskId: 2217930
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
taskId: 2217930
</pre>
</div>
</content>
</entry>
<entry>
<title>[IMP] *: declare ir.rule in noupdate</title>
<updated>2020-03-20T15:21:25+00:00</updated>
<author>
<name>Victor Feyens</name>
<email>vfe@odoo.com</email>
</author>
<published>2020-03-10T17:07:12+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=a3ded9043d34229e4547e16625a86dfbebdbcfaf'/>
<id>a3ded9043d34229e4547e16625a86dfbebdbcfaf</id>
<content type='text'>
ir.rule are default values but can be customized based on the
company's policy and needs.
This is typically a record that is in noupdate as should be
customization-friendly.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
ir.rule are default values but can be customized based on the
company's policy and needs.
This is typically a record that is in noupdate as should be
customization-friendly.
</pre>
</div>
</content>
</entry>
<entry>
<title>[ADD] timer: New mixin to record time on models</title>
<updated>2020-02-05T15:44:37+00:00</updated>
<author>
<name>Okan SUMER (osu)</name>
<email>osu@odoo.com</email>
</author>
<published>2020-02-05T15:15:29+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=e2b749fb7a441b4337c40cc856459e2e5f95b597'/>
<id>e2b749fb7a441b4337c40cc856459e2e5f95b597</id>
<content type='text'>
Purpose
=======

The timer mechanism is already existing on timesheet.

We would like to introduce it on helpdesk.ticket too, and
probably on other models afterward.

On the other hand, only one timer can be launched on a single
timesheet currently, shared amongst the different users.

This commit introduced a new mixin on which
- Each user can launch a timer on each record of the models
  inheriting the mixin.
- Launching a new timer on a record pauses the timer of the
  user that could be already running.
- The mixin brings methods to start/stop/pause/resume the
  timer, that could be overridden to implement a specific
  behavior for the related model, for example create a
  timesheet entry.

TaskID: 2149450
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Purpose
=======

The timer mechanism is already existing on timesheet.

We would like to introduce it on helpdesk.ticket too, and
probably on other models afterward.

On the other hand, only one timer can be launched on a single
timesheet currently, shared amongst the different users.

This commit introduced a new mixin on which
- Each user can launch a timer on each record of the models
  inheriting the mixin.
- Launching a new timer on a record pauses the timer of the
  user that could be already running.
- The mixin brings methods to start/stop/pause/resume the
  timer, that could be overridden to implement a specific
  behavior for the related model, for example create a
  timesheet entry.

TaskID: 2149450
</pre>
</div>
</content>
</entry>
</feed>
