← Back to parent Epic
MAZENG-FT-4 · Maintain personal profile details
Why it matters
A user needs their displayed identity and supported contact details to remain accurate.
Expected outcome
Keeps activity and collaboration attributable to the correct person.
In scope
- View the current personal profile.
- Update first name and last name.
- Update contact details that are explicitly retained in Next Gen scope.
- Delivery status
IN_BACKLOG- Owner
- RootAtSkic (product lead)
- Solution approval
- PENDING
Acceptance
Acceptance outcomes
- 01
The profile displays the user's current supported details.
- 02
Valid edits persist and remain visible after reload.
- 03
Missing required names or otherwise invalid edits are rejected with visible feedback and do not replace the prior valid values.
Dependencies and risks
Dependencies
None recorded.
Risks
- Whether mobile number and profile image are supported or required Next Gen fields remains undecided.
- Legacy client and API field support differ: the client edits names while the API also accepts a mobile number.
Authoritative Architecture tasks
No authoritative Architecture tasks are linked.