← Back to team overview

openerp-india team mailing list archive

[Bug 1285866] [NEW] [trunk/7.0]OE chatter's tracking doesn't support m2m or one2many

 

Public bug reported:

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

** Affects: ocb-addons
     Importance: Undecided
         Status: New

** Affects: openobject-addons
     Importance: Undecided
         Status: New


** Tags: 7.0 chatter m2m mail o2m trunk

** Description changed:

  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
+ * first entry.. * second entry
+ ............. → * third entry
+ ................* fourth entry
  
  or:
  Test object:
  * Added:
- ** second entry
- ** third entry
- ** fourth entry
+   ** second entry
+   ** third entry
+   ** fourth entry
  * Removed:
- ** first entry
+   ** first entry
  
  Actual output:
  The chatter will log something along the lines of:
  Test object: [1] → [2, 3, 4]
  
  Versions:
  server: r5248
  addons: r9856

** Description changed:

  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
+ * first entry   * second entry
+               → * third entry
+                 * fourth entry
  
  or:
  Test object:
  * Added:
-   ** second entry
-   ** third entry
-   ** fourth entry
+   * second entry
+   * third entry
+   * fourth entry
  * Removed:
-   ** first entry
+   * first entry
  
  Actual output:
  The chatter will log something along the lines of:
  Test object: [1] → [2, 3, 4]
  
  Versions:
  server: r5248
  addons: r9856

** Description changed:

  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
+ * 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

** Also affects: ocb-addons
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/1285866

Title:
  [trunk/7.0]OE chatter's tracking doesn't support m2m or one2many

Status in OpenERP Community Backports (Addons):
  New
Status in OpenERP Addons (modules):
  New

Bug 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ocb-addons/+bug/1285866/+subscriptions


Follow ups

References