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

feat(custom-fields): add required flag to custom field definitions #597

New Issue
Open
opened 2026-06-10 04:05:57 +00:00 by jmiller · 0 comments
jmiller commented 2026-06-10 04:05:57 +00:00
Owner
Copy Link
Copy Source

Summary

Custom fields should support a required flag so that org admins can mark specific fields as mandatory when creating or editing issues.

Changes needed

  • Add is_required column to custom_field table
  • Add required checkbox to org custom field settings UI
  • Validate required fields on issue create/edit (API + web)
  • Show required indicator (*) in issue sidebar and forms

Acceptance criteria

  • Custom field definition has is_required boolean
  • Org settings UI shows required toggle per field
  • Issue create/edit rejects submission if required fields are empty
  • API returns validation error for missing required fields
  • Required fields show visual indicator in the UI
## Summary Custom fields should support a `required` flag so that org admins can mark specific fields as mandatory when creating or editing issues. ## Changes needed - Add `is_required` column to `custom_field` table - Add required checkbox to org custom field settings UI - Validate required fields on issue create/edit (API + web) - Show required indicator (*) in issue sidebar and forms ## Acceptance criteria - [ ] Custom field definition has `is_required` boolean - [ ] Org settings UI shows required toggle per field - [ ] Issue create/edit rejects submission if required fields are empty - [ ] API returns validation error for missing required fields - [ ] Required fields show visual indicator in the UI
Sign in to join this conversation.
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#597
Delete Branch "%!s()"

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?