Transfer System #13

Open
opened 2025-09-16 11:46:17 -05:00 by Ajdj100 · 2 comments
Member
  • User can post transfer request
  • Admin can force transfer member
  • HQ can comment on transfer request to approve or deny
  • Admin can approve transfer request which causes the members status to be changed
  • Command/admin can see a list of all historical transfer requests and their resolutions (similar to LOA history interface)
- [ ] User can post transfer request - [ ] Admin can force transfer member - [ ] HQ can comment on transfer request to approve or deny - [ ] Admin can approve transfer request which causes the members status to be changed - [ ] Command/admin can see a list of all historical transfer requests and their resolutions (similar to LOA history interface)
Author
Member

We are shrinking the scope of this for now. Originally approval was to be fully automated based on approval from all involved commanders, now commanders can comment their approval and whatever details they need, and admin can click the approve button to move the company.

Admin will also need to manually set the users new rank via the "promotions" interface after the transfer. We can look at streamlining this more post 1.0

We are shrinking the scope of this for now. Originally approval was to be fully automated based on approval from all involved commanders, now commanders can comment their approval and whatever details they need, and admin can click the approve button to move the company. Admin will also need to manually set the users new rank via the "promotions" interface after the transfer. We can look at streamlining this more post 1.0
Author
Member

Current status of this PR is that the UI exists to submit a transfer request. This UI is not hooked up to anything yet.

A placeholder UI exists for the approval system but needs to be overhauled to align with the current direction of the issue.

the status_change_requests table in the database is for holding transfer requests

next to no API systems have been created for this. You can check api\src\routes\statuses.js and api\src\services\statusService.ts for what little does exist.

Current status of this PR is that the UI exists to submit a transfer request. This UI is not hooked up to anything yet. A placeholder UI exists for the approval system but needs to be overhauled to align with the current direction of the issue. the status_change_requests table in the database is for holding transfer requests next to no API systems have been created for this. You can check `api\src\routes\statuses.js` and `api\src\services\statusService.ts` for what little does exist.
Ajdj100 added the Kind/Feature label 2025-11-10 12:50:19 -06:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: 17th-Ranger-Battalion-ORG/milsim-site-v4#13