Handing the visit to someone else, without the technician choosing who.
Status at ebf7cf0: Gap — the outcome is recorded on the current Job Log, but the follow-up Job Log is not created automatically. Older aliases are still accepted.
A technician records outcome = reassign with a reason.
| Means | |
|---|---|
reassign |
A different technician or team is required. |
sambung_kerja |
The same work continues in another visit. |
Both create a new unscheduled draft; they differ in why.
Story. As a Technician, I want to record Reassign with a reason, so that the current visit ends without choosing the replacement person or date.
Acceptance. The reason is required and the existing visit retains its evidence.
Story. As OE, I want a new unscheduled Draft Job Log in my queue, so that I can choose the next Technician and date.
Acceptance. The new Job Log links to the same Order and identifies the source visit.
The outcome is recorded on the current Job Log, but the required follow-up Job Log is not created automatically. Older aliases are still accepted by the endpoint — the code showed "Reassigned to OE" among seven internal names that must be merged down to the six canonical outcomes.
New to these terms? See the Glossary.