Tryton - Issues

 

Issue9298

Title strange behavior on o2m fields with many2many widget
Priority bug Status chatting
Superseder Nosy List ced, oqueralto, pokoli
Type behavior Components sao, tryton
Assigned To Keywords
Reviews

Created on 2020-05-05.14:46:17 by oqueralto, last changed by ced.

Messages
msg57841 (view) Author: [hidden] (ced) (Tryton committer) (Tryton translator) Date: 2020-05-05.16:28:11
I think it is linked to issue3325.
msg57840 (view) Author: [hidden] (oqueralto) Date: 2020-05-05.16:20:09
It's happening on both.
msg57839 (view) Author: [hidden] (pokoli) (Tryton committer) (Tryton translator) Date: 2020-05-05.16:05:02
Are you using tryton, sao or both?
msg57836 (view) Author: [hidden] (oqueralto) Date: 2020-05-05.14:46:16
It happens on any o2m field with the many2one widget, but I will explain how to reproduce it on a concrete one:

1. Create a new Supplier shipment. 
2. Add an existing incoming move to the shipment.
3. Open the move form. 
4. Press cancel button or 'Esc' key.
5. Save the shipment or receive it.

If you follow the steps, the move disappears, but for me the expected behavior is to keep it.

I'm using 5.2 version but it's also happening in 5.6.
History
Date User Action Args
2020-05-05 16:28:12cedsetnosy: + ced
messages: + msg57841
2020-05-05 16:25:27pokolisetcomponent: + tryton, sao
2020-05-05 16:20:09oqueraltosetmessages: + msg57840
2020-05-05 16:05:03pokolisetstatus: unread -> chatting
nosy: + pokoli
messages: + msg57839
2020-05-05 14:46:17oqueraltocreate

Showing 10 items. Show all history (warning: this could be VERY long)