| 2014-02-27 21:06:44 |
Sandy Carter (http://www.savoirfairelinux.com) |
bug |
|
|
added bug |
| 2014-02-27 21:07:36 |
Sandy Carter (http://www.savoirfairelinux.com) |
description |
I have a model which inherits mail.thread. On this model I have enabled track_visibility='onchange' on many of the fields.
The widget logs all changes done to fields.char, fields.selection in a way that is natural.
When it comes to fields.many2many and fields.one2many, what is logged is a string representation of the list of the foreign object ids.
Steps to reproduce:
* Create a module with an object which inherits 'mail.thread', add a many2many or a one2many relational field.
* Create the view with the fields and the chatter section
* Modify the field
* Save changes
Expected output:
The chatter will log something along the lines of:
Test object:
* first entry......... * second entry
....................... → .. * third entry
...............................* fourth entry
or:
Test object:
* Added:
** second entry
** third entry
** fourth entry
* Removed:
** first entry
Actual output:
The chatter will log something along the lines of:
Test object: [1] → [2, 3, 4]
Versions:
server: r5248
addons: r9856 |
I have a model which inherits mail.thread. On this model I have enabled track_visibility='onchange' on many of the fields.
The widget logs all changes done to fields.char, fields.selection in a way that is natural.
When it comes to fields.many2many and fields.one2many, what is logged is a string representation of the list of the foreign object ids.
Steps to reproduce:
* Create a module with an object which inherits 'mail.thread', add a many2many or a one2many relational field.
* Create the view with the fields and the chatter section
* Modify the field
* Save changes
Expected output:
The chatter will log something along the lines of:
Test object:
* first entry.. * second entry
............. → * third entry
................* fourth entry
or:
Test object:
* Added:
** second entry
** third entry
** fourth entry
* Removed:
** first entry
Actual output:
The chatter will log something along the lines of:
Test object: [1] → [2, 3, 4]
Versions:
server: r5248
addons: r9856 |
|
| 2014-02-27 21:08:03 |
Sandy Carter (http://www.savoirfairelinux.com) |
description |
I have a model which inherits mail.thread. On this model I have enabled track_visibility='onchange' on many of the fields.
The widget logs all changes done to fields.char, fields.selection in a way that is natural.
When it comes to fields.many2many and fields.one2many, what is logged is a string representation of the list of the foreign object ids.
Steps to reproduce:
* Create a module with an object which inherits 'mail.thread', add a many2many or a one2many relational field.
* Create the view with the fields and the chatter section
* Modify the field
* Save changes
Expected output:
The chatter will log something along the lines of:
Test object:
* first entry.. * second entry
............. → * third entry
................* fourth entry
or:
Test object:
* Added:
** second entry
** third entry
** fourth entry
* Removed:
** first entry
Actual output:
The chatter will log something along the lines of:
Test object: [1] → [2, 3, 4]
Versions:
server: r5248
addons: r9856 |
I have a model which inherits mail.thread. On this model I have enabled track_visibility='onchange' on many of the fields.
The widget logs all changes done to fields.char, fields.selection in a way that is natural.
When it comes to fields.many2many and fields.one2many, what is logged is a string representation of the list of the foreign object ids.
Steps to reproduce:
* Create a module with an object which inherits 'mail.thread', add a many2many or a one2many relational field.
* Create the view with the fields and the chatter section
* Modify the field
* Save changes
Expected output:
The chatter will log something along the lines of:
Test object:
* first entry * second entry
→ * third entry
* fourth entry
or:
Test object:
* Added:
* second entry
* third entry
* fourth entry
* Removed:
* first entry
Actual output:
The chatter will log something along the lines of:
Test object: [1] → [2, 3, 4]
Versions:
server: r5248
addons: r9856 |
|
| 2014-02-27 21:08:27 |
Sandy Carter (http://www.savoirfairelinux.com) |
description |
I have a model which inherits mail.thread. On this model I have enabled track_visibility='onchange' on many of the fields.
The widget logs all changes done to fields.char, fields.selection in a way that is natural.
When it comes to fields.many2many and fields.one2many, what is logged is a string representation of the list of the foreign object ids.
Steps to reproduce:
* Create a module with an object which inherits 'mail.thread', add a many2many or a one2many relational field.
* Create the view with the fields and the chatter section
* Modify the field
* Save changes
Expected output:
The chatter will log something along the lines of:
Test object:
* first entry * second entry
→ * third entry
* fourth entry
or:
Test object:
* Added:
* second entry
* third entry
* fourth entry
* Removed:
* first entry
Actual output:
The chatter will log something along the lines of:
Test object: [1] → [2, 3, 4]
Versions:
server: r5248
addons: r9856 |
I have a model which inherits mail.thread. On this model I have enabled track_visibility='onchange' on many of the fields.
The widget logs all changes done to fields.char, fields.selection in a way that is natural.
When it comes to fields.many2many and fields.one2many, what is logged is a string representation of the list of the foreign object ids.
Steps to reproduce:
* Create a module with an object which inherits 'mail.thread', add a many2many or a one2many relational field.
* Create the view with the fields and the chatter section
* Modify the field
* Save changes
Expected output:
The chatter will log something along the lines of:
Test object:
* first entry.. * second entry
→ * third entry
* fourth entry
or:
Test object:
* Added:
* second entry
* third entry
* fourth entry
* Removed:
* first entry
Actual output:
The chatter will log something along the lines of:
Test object: [1] → [2, 3, 4]
Versions:
server: r5248
addons: r9856 |
|
| 2014-02-27 21:10:42 |
Sandy Carter (http://www.savoirfairelinux.com) |
bug task added |
|
ocb-addons |
|
| 2014-02-27 21:19:33 |
Sandy Carter (http://www.savoirfairelinux.com) |
attachment added |
|
Partial solution which fixes m2m, but does not fix o2m INCOMPLETE https://bugs.launchpad.net/ocb-addons/+bug/1285866/+attachment/4000090/+files/o2m_m2m_tracking_lp1285866.patch |
|
| 2014-02-27 21:23:18 |
Stéphane Bidoul (Acsone) |
bug |
|
|
added subscriber Acsone OpenErp Team |
| 2014-02-27 21:53:52 |
Launchpad Janitor |
branch linked |
|
lp:~savoirfairelinux-openerp/openobject-addons/lp1285866 |
|
| 2014-02-28 05:17:03 |
Naresh(OpenERP) |
openobject-addons: assignee |
|
OpenERP Publisher's Warranty Team (openerp-opw) |
|
| 2014-02-28 05:17:12 |
Naresh(OpenERP) |
tags |
7.0 chatter m2m mail o2m trunk |
7.0 chatter m2m mail maintenance o2m trunk |
|
| 2014-02-28 11:06:29 |
Daniel Reis |
bug |
|
|
added subscriber Daniel Reis |
| 2015-07-08 13:33:16 |
Dhinesh |
bug |
|
|
added subscriber Dhinesh |
