Tryton - Issues

 

Issue8152

Title carrier change erases ref
Priority bug Status invalid
Superseder Nosy List jcm, pokoli
Type behavior Components carrier, sale
Assigned To Keywords
Reviews

Created on 2019-02-27.16:06:15 by jcm, last changed by pokoli.

Messages
msg51405 (view) Author: [hidden] (pokoli) (Tryton committer) (Tryton translator) Date: 2019-08-22.14:27:00
I'm closing this issue because we did not get any reply in 5 months.

Please re-open with the steps to reproduct if you don't agree.
msg48015 (view) Author: [hidden] (pokoli) (Tryton committer) (Tryton translator) Date: 2019-03-25.20:11:09
So it seems some issue with the client. Which client are you using? Web client or desktop one? 

We need some steps to reproduce it in order to be able to fix it.
msg48013 (view) Author: [hidden] (jcm) Date: 2019-03-25.18:03:15
I tried on demo to reproduce it but without success. I think it's simply that I don't hit <tab> after entering a reference and then I click on the cross to remove the preselected carrier service. The reference is then erased. The strange thing is that for some fields, the value is kept event without moving to the next field, whereas for some others the value is recalculated and erases the entered one.
msg47440 (view) Author: [hidden] (pokoli) (Tryton committer) (Tryton translator) Date: 2019-03-06.11:49:15
I can not reproduce on 5.0 series

Could you indicate on which version are you working and the steps to reproduce it?
msg47245 (view) Author: [hidden] (jcm) Date: 2019-02-27.16:06:14
In Sale, if Reference field is filled before Carrier, the Reference is cleared when the carrier changes.
I expect it to leave Reference untouched.
History
Date User Action Args
2019-08-22 14:27:01pokolisetstatus: need-eg -> invalid
messages: + msg51405
2019-03-25 20:11:09pokolisetmessages: + msg48015
2019-03-25 18:03:15jcmsetmessages: + msg48013
2019-03-06 11:49:15pokolisetstatus: unread -> need-eg
nosy: + pokoli
messages: + msg47440
2019-02-27 16:06:15jcmcreate

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