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

feat: Add custom fields on issues #8

New Issue
Open
opened 2026-05-08 03:26:37 +00:00 by jmiller · 1 comment
jmiller commented 2026-05-08 03:26:37 +00:00
Owner
Copy Link
Copy Source

Track upstream progress on custom issue fields.

This would allow repos to define dropdown, date, number, and text fields on issues � enabling structured project management beyond labels.

Use Case

  • Priority/effort scoring
  • Sprint assignment
  • Client/project tagging
  • Due date tracking

Status

Not yet in upstream roadmap. Consider implementing in MokoGitea if not planned.

Track upstream progress on custom issue fields. This would allow repos to define dropdown, date, number, and text fields on issues � enabling structured project management beyond labels. ## Use Case - Priority/effort scoring - Sprint assignment - Client/project tagging - Due date tracking ## Status Not yet in upstream roadmap. Consider implementing in MokoGitea if not planned.
jmiller commented 2026-06-04 05:29:10 +00:00
Author
Owner
Copy Link
Copy Source

Progress Update

Done

  • Data model: CustomFieldDef + CustomFieldValue (EAV pattern)
  • Migration v343: creates both tables
  • Model CRUD: create/read/update/delete field definitions
  • Model values: get/set per-issue, map interface
  • Settings handler: CustomFields, CreatePost, EditPost, DeletePost
  • Settings template: table listing, create modal, edit/delete buttons
  • Route: /settings/custom-fields
  • Navbar entry with icon
  • 16 locale keys

TODO

  • Issue create/edit form: render custom fields
  • Issue view: display custom field values in sidebar
  • Save custom field values on issue create/edit POST
  • API: custom field values in issue response
  • Search/filter by custom field values
  • Edit modal JS (populate form from data attributes)
## Progress Update ### Done - [x] Data model: CustomFieldDef + CustomFieldValue (EAV pattern) - [x] Migration v343: creates both tables - [x] Model CRUD: create/read/update/delete field definitions - [x] Model values: get/set per-issue, map interface - [x] Settings handler: CustomFields, CreatePost, EditPost, DeletePost - [x] Settings template: table listing, create modal, edit/delete buttons - [x] Route: /settings/custom-fields - [x] Navbar entry with icon - [x] 16 locale keys ### TODO - [ ] Issue create/edit form: render custom fields - [ ] Issue view: display custom field values in sidebar - [ ] Save custom field values on issue create/edit POST - [ ] API: custom field values in issue response - [ ] Search/filter by custom field values - [ ] Edit modal JS (populate form from data attributes)
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 Medium
Type Feature
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#8
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?