Resolve "Set rider's current jo id to null if JO's hub is reassigned and JO has been rider assigned" #1600
No reviewers
Labels
No labels
API
AU
Bug
CRM Enhancements
Mobile API
Nice to have
Phase 2
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: rgutierrez/resq#1600
Loading…
Reference in a new issue
No description provided.
Delete branch "675-set-rider-s-current-jo-id-to-null-if-jo-s-hub-is-reassigned-and-jo-has-been-rider-assigned"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #675
assigned to @korina.cordero
added 1 commit
60988583- Fix issue of rider assignment not working after hub reassignment. #675Compare with previous version
marked this merge request as ready
added 5 commits
mastere3652352- Merge branch 'master' of gitlab.com:jankstudio/resq into...c3ecf514- Add checking for current job order. #675Compare with previous version
added 1 commit
e2bdf91f- Add checking for current job order that current jo is the selected jo. #675Compare with previous version
mentioned in commit
79f2686404