MokoConsulting/MokoGitea-APP
1
0
Fork 0
Code Issues 171 Pull Requests 1 Releases 96 Wiki Activity

feat(custom-fields): add required flag UI and API validation (#597) #612

Merged
jmiller merged 1 commits from feature/597-required-custom-fields into main 2026-06-12 02:59:24 +00:00
Conversation 0 Commits 1 Files Changed 3
+21 -2
jmiller commented 2026-06-12 02:50:24 +00:00
Owner
Copy Link
Copy Source

Summary

Adds the missing UI and API validation for the required flag on custom field definitions.

Changes

  • Org settings custom fields form: added Required checkbox
  • Field list table: shows red asterisk (*) on required fields
  • API issue create: validates required custom fields, returns 422 if missing
  • Added locale strings for required field UI

Notes

The Required boolean already exists in the DB (migration v343), API responses, and web form validation. This PR adds the missing pieces: the org settings UI to set it, and API-side validation.

Closes #597

## Summary Adds the missing UI and API validation for the `required` flag on custom field definitions. ## Changes - Org settings custom fields form: added Required checkbox - Field list table: shows red asterisk (*) on required fields - API issue create: validates required custom fields, returns 422 if missing - Added locale strings for required field UI ## Notes The `Required` boolean already exists in the DB (migration v343), API responses, and web form validation. This PR adds the missing pieces: the org settings UI to set it, and API-side validation. Closes #597
jmiller added 1 commit 2026-06-12 02:50:27 +00:00
feat(custom-fields): add required flag UI and API validation (#597)
Generic: Project CI / Tests (pull_request) Blocked by required conditions
Details
Universal: PR Check / Build RC Package (pull_request) Blocked by required conditions
Details
Universal: PR Check / Report Issues (pull_request) Blocked by required conditions
Details
Branch Policy Check / Verify merge target (pull_request) Failing after 4s
Details
Generic: Repo Health / Scripts governance (pull_request) Blocked by required conditions
Details
Universal: PR Check / Branch Policy (pull_request) Failing after 4s
Details
Generic: Repo Health / Repository health (pull_request) Blocked by required conditions
Details
Generic: Repo Health / Report Issues (pull_request) Blocked by required conditions
Details
Generic: Repo Health / Site Health (pull_request) Has been skipped
Details
Universal: PR Check / Validate PR (pull_request) Failing after 15s
Details
Generic: Repo Health / Access control (pull_request) Successful in 5s
Details
Generic: Repo Health / Scripts governance (push) Blocked by required conditions
Details
Generic: Repo Health / Repository health (push) Blocked by required conditions
Details
Generic: Repo Health / Report Issues (push) Blocked by required conditions
Details
Generic: Project CI / Lint & Validate (pull_request) Successful in 1m0s
Details
Generic: Repo Health / Site Health (push) Has been skipped
Details
Generic: Repo Health / Access control (push) Successful in 3s
Details
Branch Cleanup / Delete merged branch (pull_request) Has been skipped
Details
RC Revert / Rename rc/ back to dev/ (pull_request) Has been skipped
Details
PR RC Release / Build RC Release (pull_request) Failing after 1m30s
Details
Universal: Auto Version Bump / Version Bump (push) Successful in 11s
Details
Universal: Build & Release / Promote to RC (pull_request) Has been skipped
Details
Universal: Build & Release / Build & Release Pipeline (pull_request) Has been skipped
Details
Universal: Secret Scanning / Gitleaks Secret Scan (pull_request) Successful in 2m37s
Details
245b5a8e6a 
- Add required checkbox to org custom field settings form
- Show red asterisk (*) indicator on required fields in the list
- Validate required custom fields on API issue create (return 422)
- Add locale strings for required field UI

The Required column already exists in the DB (migration v343) and is
already validated in the web form. This adds the missing org settings
UI checkbox and API-side validation.

Co-Authored-By: Moko Consulting <hello@mokoconsulting.tech>
jmiller closed this pull request 2026-06-12 02:51:12 +00:00
jmiller deleted branch feature/597-required-custom-fields 2026-06-12 02:51:21 +00:00
jmiller reopened this pull request 2026-06-12 02:58:49 +00:00
jmiller merged commit ece24c6d38 into main 2026-06-12 02:59:24 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
breaking-change
Breaking API or behavior change
 ci-cd
CI/CD pipeline changes
 config
Configuration changes
 dependencies
Dependency updates
 deploy-failure
Deployment failed
 docker
Docker/container changes
 documentation
Documentation changes
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 mokostandards
Related to MokoStandards framework
 push-failure
Git push operation failed
 security
Security vulnerability or hardening
 size/l
200-500 lines changed
 size/m
50-200 lines changed
 size/s
10-50 lines changed
 size/xl
500+ lines changed
 size/xs
< 10 lines changed
 standards-drift
Deviates from MokoStandards
 standards-update
MokoStandards compliance update
 sync-failure
Sync or mirror failed
 tech-debt
Technical debt and TODO/FIXME items
 upstream
upstream
Inherited from upstream Gitea
 work-in-progress
Draft or incomplete work
No labels
Priority -
Type -
Status —
Priority —
Type —
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller) moko-deploy (Moko Deploy Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGitea-APP#612
Delete Branch "feature/597-required-custom-fields"

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?