Tuesday, June 29, 2021
3 changes · master
Resolved issues and error corrections
When a message delivery failure is resent or ignored by someone other than the original author, the notification status now updates immediately on screen. This prevents confusion by clearly showing that the issue has been handled without requiring a manual page refresh.
Original PR description
**Current behavior before PR:** Currently, failure notifications are sent to the author of the message that the failure is concerning. However, if another user than the author is resolving the failure, he is not receiving any notification without refresh the page, so it appears as if nothing happened even though the failure was indeed resolved (either message resent, or failure ignored). **Desired behavior after PR is merged:** When another user than the author update the status of the failure notification (message resent or failure ignored). the statues of the failure notification update instantly, no refresh needed to show the updated status. **LINKS:** Task-2178257 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixed an issue where clicking a phone number in a form could crash when VoIP was installed. Users can now start calls normally and see the expected notification, reducing disruption for teams using phone integrations.
Original PR description
Before this commit, it crashed when you clicked on a phone number in a form view, with voip installed. A call to the notification service was still using the former api.
Failure notifications now refresh immediately when another user resends a message or ignores the failure. This prevents users from seeing outdated failure information and avoids needing to manually refresh the page to confirm the issue was handled.
Original PR description
Current behavior before PR:
Currently, failure notifications are sent to the author of the message that the
failure is concerning.
However, if another user than the author is resolving the failure, he is not
receiving any notification without refresh the page, so it appears as if nothing
happened even though the failure was indeed resolved
(either message resent, or failure ignored).
Desired behavior after PR is merged:
When another user than the author updates the status of the failure notification
(message resent or failure ignored). the status of the failure notification update
instantly, no refresh needed to show the updated status.
Task-2178257