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

feat(issues): make status_id, priority_id, type_id required on issue create #598

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

Summary

The status_id, priority_id, and type_id fields should be required when creating issues, not optional. This ensures every issue has proper metadata from the start.

Changes needed

API

  • modules/structs/issue.go: Change CreateIssueOption fields from *int64 (optional) to int64 (required)
  • routers/api/v1/repo/issue.go: Validate non-zero values on create, return 422 if missing
  • Auto-assign org defaults when not provided (use is_default definitions)

MCP

  • mcp-mokogitea-api/src/index.ts: Change status_id, priority_id, type_id from z.number().optional() to z.number() on gitea_issue_create
  • Keep optional on gitea_issue_update (partial updates)

Web UI

  • Issue create form should pre-select default status/priority/type
  • Prevent submission without selections
## Summary The `status_id`, `priority_id`, and `type_id` fields should be required when creating issues, not optional. This ensures every issue has proper metadata from the start. ## Changes needed ### API - `modules/structs/issue.go`: Change `CreateIssueOption` fields from `*int64` (optional) to `int64` (required) - `routers/api/v1/repo/issue.go`: Validate non-zero values on create, return 422 if missing - Auto-assign org defaults when not provided (use `is_default` definitions) ### MCP - `mcp-mokogitea-api/src/index.ts`: Change `status_id`, `priority_id`, `type_id` from `z.number().optional()` to `z.number()` on `gitea_issue_create` - Keep optional on `gitea_issue_update` (partial updates) ### Web UI - Issue create form should pre-select default status/priority/type - Prevent submission without selections
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#598
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?