Prevent JO progression on rider app after cancellation #793

Open
opened 2024-03-19 06:47:48 +00:00 by arcticzero · 8 comments
arcticzero commented 2024-03-19 06:47:48 +00:00 (Migrated from gitlab.com)

Rider app can still progress JO status if it is their currently active JO, even after CRM has cancelled it. Not sure if old rider app handles the cancelled MQTT event, but creating failsafe in case MQTT is not working.

Rider app can still progress JO status if it is their currently active JO, even after CRM has cancelled it. Not sure if old rider app handles the cancelled MQTT event, but creating failsafe in case MQTT is not working.
arcticzero commented 2024-03-19 06:47:48 +00:00 (Migrated from gitlab.com)

assigned to @arcticzero

assigned to @arcticzero
arcticzero commented 2024-03-19 06:48:17 +00:00 (Migrated from gitlab.com)

created branch 793-prevent-jo-progression-on-rider-app-after-cancellation to address this issue

created branch [`793-prevent-jo-progression-on-rider-app-after-cancellation`](/jankstudio/resq/-/compare/master...793-prevent-jo-progression-on-rider-app-after-cancellation) to address this issue
arcticzero commented 2024-03-19 07:22:39 +00:00 (Migrated from gitlab.com)

mentioned in commit 9152370300

mentioned in commit 9152370300fd1fe4af02dd625cce35c05851f5a2
arcticzero commented 2024-03-19 07:25:37 +00:00 (Migrated from gitlab.com)

mentioned in commit ca513355fe

mentioned in commit ca513355fe74970e377e02de9c058e3560a0a869
arcticzero commented 2024-03-19 08:33:39 +00:00 (Migrated from gitlab.com)

mentioned in merge request !904

mentioned in merge request !904
arcticzero commented 2024-03-19 08:35:56 +00:00 (Migrated from gitlab.com)

mentioned in commit 1a6af00399

mentioned in commit 1a6af003996d0344dd4d6d22bb688a089ca33cb1
arcticzero commented 2024-03-19 08:36:16 +00:00 (Migrated from gitlab.com)

mentioned in merge request !905

mentioned in merge request !905
arcticzero commented 2024-03-19 08:36:24 +00:00 (Migrated from gitlab.com)

mentioned in commit cd21e41d2f

mentioned in commit cd21e41d2f9f25e26fd3ac1ca42fa17d52d017e0
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: rgutierrez/resq#793
No description provided.