FOUR-32981: Show job title validation errors

[eiresendez]

Issue & Reproduction Steps

Editing a user with HTML markup in the Job Title field returns a 422 validation response, but the form does not display the errors.title message. The save appears to fail without identifying the invalid field.

1. Open an existing user in Admin > Users.
2. Enter HTML markup in Job Title while keeping the other fields valid.
3. Save the user.
4. Observe the 422 response and the missing field-level validation feedback.

Solution

• Bind the Job Title input to the API's errors.title state.
• Render the first Job Title validation message below the input.
• Initialize and reset the title error in both the administrator and personal profile edit flows.
• Add feature coverage confirming both edit views render the validation contract.

How to Test

Manual validation confirmed that an invalid Job Title on the administrator user edit page is highlighted and displays The title field must contain plain text only.

1. Open /admin/users/{id}/edit, enter HTML markup only in Job Title, and save.
2. Confirm Job Title is marked invalid and shows the API validation message.
3. Replace the markup with plain text and confirm the user saves successfully.
4. Repeat the same invalid and valid cases on /profile/edit.
5. Confirm First Name and Last Name validation feedback remains unchanged.

The focused automated test was not run because the safe Laravel test wrapper rejected this checkout: .env.testing is missing. Run tests/Feature/Admin/UserTest.php through the repository's isolated SQLite test environment.

Related Tickets & Packages

• https://processmaker.atlassian.net/browse/FOUR-32981
• ProcessMaker core only; no package changes are required.

ci:deploy

[decisions-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[eiresendez]

Hi @nolanpro @sanjacornelius, just a heads-up that the deployments are failing in EKS across some PRs. Another recent PR encountered the same Helm and environment-readiness failure with a different CI instance.

[nolanpro]

QA server K8S was successfully deployed https://ci-118bf1e2fe.engk8s.processmaker.net

[nolanpro]

Hi @nolanpro @sanjacornelius, just a heads-up that the deployments are failing in EKS across some PRs. Another recent PR encountered the same Helm and environment-readiness failure with a different CI instance.

Should be working now

[CarliPinell]

The code looks good. No observations.

[CarliPinell]

No observations were found.