<feed xmlns='http://www.w3.org/2005/Atom'>
<title>Odoo/addons/rating_project/data/project_demo.xml, 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>[REM] rating_project: kill the module and move feature in project</title>
<updated>2017-12-12T13:06:29+00:00</updated>
<author>
<name>Jérome Maes</name>
<email>jem@openerp.com</email>
</author>
<published>2017-10-23T14:02:55+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=95698bd408a29cb2ebc4abe0445a4739eceba082'/>
<id>95698bd408a29cb2ebc4abe0445a4739eceba082</id>
<content type='text'>
Impacted modules: project, rating_project,
sale_service_rating and website_rating_project.

Removed modules: rating_project and sale_service_rating.

Move code to empty 'rating_project' module, in order
to kill it.
Code is not modified, simply copy/paste at the right
place in 'project' module code.

However, 'enable rating on task' options is convert
into a res.groups that can be activated from the
project settings.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Impacted modules: project, rating_project,
sale_service_rating and website_rating_project.

Removed modules: rating_project and sale_service_rating.

Move code to empty 'rating_project' module, in order
to kill it.
Code is not modified, simply copy/paste at the right
place in 'project' module code.

However, 'enable rating on task' options is convert
into a res.groups that can be activated from the
project settings.
</pre>
</div>
</content>
</entry>
<entry>
<title>[IMP] rating_project: change demo data</title>
<updated>2017-03-23T08:59:57+00:00</updated>
<author>
<name>Jérome Maes</name>
<email>jem@openerp.com</email>
</author>
<published>2017-02-08T15:55:26+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=330fe871bca54ebd4404475fd5538f3e299c676d'/>
<id>330fe871bca54ebd4404475fd5538f3e299c676d</id>
<content type='text'>
Since we want to remove portal module, this
xmlid will not make sense anymore.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Since we want to remove portal module, this
xmlid will not make sense anymore.
</pre>
</div>
</content>
</entry>
<entry>
<title>[IMP] rating: delete rating when needed</title>
<updated>2017-01-09T15:33:21+00:00</updated>
<author>
<name>Jérome Maes</name>
<email>jem@openerp.com</email>
</author>
<published>2016-12-06T14:29:29+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=8e10f6adf9ec8e3e3a4fcdbbca627f0dc4dcf742'/>
<id>8e10f6adf9ec8e3e3a4fcdbbca627f0dc4dcf742</id>
<content type='text'>
Automatically deleting a rating was not implemented
yet. We find 2 cases :
- when uninstalling a module, the same mecanism as
mail.follower is used, via a res_model_id field
pointing on ir.model. When this model does not
exist anymore, remove all related rating.
- when deleting a record, its rating should be
deleted too.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Automatically deleting a rating was not implemented
yet. We find 2 cases :
- when uninstalling a module, the same mecanism as
mail.follower is used, via a res_model_id field
pointing on ir.model. When this model does not
exist anymore, remove all related rating.
- when deleting a record, its rating should be
deleted too.
</pre>
</div>
</content>
</entry>
<entry>
<title>[REF] various: rename openerp node to odoo in xml files</title>
<updated>2016-08-10T13:48:10+00:00</updated>
<author>
<name>Thibault Delavallée</name>
<email>tde@openerp.com</email>
</author>
<published>2016-08-10T13:18:46+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=efd55ab8a50438c1398eb963e5f2cc2a1af86ef9'/>
<id>efd55ab8a50438c1398eb963e5f2cc2a1af86ef9</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>[REF,IMP] project,project_issue,rating: Handle ratings more efficiently</title>
<updated>2016-07-01T12:05:03+00:00</updated>
<author>
<name>jat-odoo</name>
<email>jat@openerp.com</email>
</author>
<published>2016-07-01T11:33:14+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=0b1a27a3c7862bbe511614d05e04db696fcd71d5'/>
<id>0b1a27a3c7862bbe511614d05e04db696fcd71d5</id>
<content type='text'>
Purpose:

For our internal project management, we would like to track the customer
satisfaction on the open projects. We send them an email every one or 2
weeks allowing them to give a feedback by clicking on one of 3
smileys: Happy, Average, Angry. They can also put a additional explanation.

We already have something similar which is working on livechat with a
unusable reporting, and on issues but unusable. Our project are managed by tasks.

Specification:
- On the project : Selection fields : (Periodical Rating or Rating on Stage)
  + Fields to choose the period if periodical
- On the stage : email_template_id field.
- IF :
---&gt; Periodical : Send an email to all the customers for the tasks on this stage periodically
---&gt; On Stage : Send an email to the customer's tasks when the task reaches the stage
- That way, it's impossible to send a satisfaction request both periodically and sequentially.
  FP request
- Who is the customer : The customer on the task OR the customer on the related sales order
  OR the customer on the projet OR nobody
- The last feedback is displayed on the task kanban card (Thumb up, down, or neutral)
- On the project kanban card, the customer satisfaction is displayed. This is the simple
  mean of all the previous ratings.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Purpose:

For our internal project management, we would like to track the customer
satisfaction on the open projects. We send them an email every one or 2
weeks allowing them to give a feedback by clicking on one of 3
smileys: Happy, Average, Angry. They can also put a additional explanation.

We already have something similar which is working on livechat with a
unusable reporting, and on issues but unusable. Our project are managed by tasks.

Specification:
- On the project : Selection fields : (Periodical Rating or Rating on Stage)
  + Fields to choose the period if periodical
- On the stage : email_template_id field.
- IF :
---&gt; Periodical : Send an email to all the customers for the tasks on this stage periodically
---&gt; On Stage : Send an email to the customer's tasks when the task reaches the stage
- That way, it's impossible to send a satisfaction request both periodically and sequentially.
  FP request
- Who is the customer : The customer on the task OR the customer on the related sales order
  OR the customer on the projet OR nobody
- The last feedback is displayed on the task kanban card (Thumb up, down, or neutral)
- On the project kanban card, the customer satisfaction is displayed. This is the simple
  mean of all the previous ratings.
</pre>
</div>
</content>
</entry>
<entry>
<title>[IMP] website_rating_project_issue: remove public projects</title>
<updated>2015-08-14T11:19:04+00:00</updated>
<author>
<name>Damien Bouvy</name>
<email>dbo@odoo.com</email>
</author>
<published>2015-08-10T14:28:57+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=6ca900ab01db9fc476267c939d6cf636595e6c96'/>
<id>6ca900ab01db9fc476267c939d6cf636595e6c96</id>
<content type='text'>
- remove public project
- some data was depending on demo data, moved it to demo
- add website_published mixin on projects
- remove project members from frontend view

Since public projects do not exist anymore, project.project objects now have the website_published mixin; any project with the rating activated and published on the website will be visible in the "Project Customer Satisfaction" link for public users
The frontend template has also been modified to remove the team members photo since project members have disappeared as of 9398fe9 by our dear @tde-banana-odoo
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
- remove public project
- some data was depending on demo data, moved it to demo
- add website_published mixin on projects
- remove project members from frontend view

Since public projects do not exist anymore, project.project objects now have the website_published mixin; any project with the rating activated and published on the website will be visible in the "Project Customer Satisfaction" link for public users
The frontend template has also been modified to remove the team members photo since project members have disappeared as of 9398fe9 by our dear @tde-banana-odoo
</pre>
</div>
</content>
</entry>
<entry>
<title>[ADD] rating_project, rating_project_issue : using the rating mixin, tasks and issues are rated when their stage changed. A email template is sent to the customer of the object.</title>
<updated>2015-01-08T11:28:22+00:00</updated>
<author>
<name>aja-odoo</name>
<email>aja@openerp.com</email>
</author>
<published>2015-01-08T10:33:35+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=c8581af5921c0b5deb780658926d0953023b2a0d'/>
<id>c8581af5921c0b5deb780658926d0953023b2a0d</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
</feed>
