Deploy issue metadata API — status, priority, type first-class fields #596

New Issue

2026-06-09T21:11:48Z

jmiller commented

2026-06-09 21:11:48 +00:00

Summary

PR #591 merged to main. The new binary needs to be built and deployed to enable the issue metadata API endpoints.

What Was Merged

First-class status_id, priority_id, type_id fields on issues
Org-level definition endpoints: /orgs/{org}/issue-statuses, /issue-priorities, /issue-types
Issue JSON includes status_name, priority_name, type_name resolved from IDs
PATCH/POST on issues accepts status_id, priority_id, type_id
Migration v355 for manifest metadata fields
Org wiki tab with internal/external mode

Deploy Steps

Build MokoGitea-APP from main branch (make build or go build)
Stop the running Gitea service
Replace the binary
Start the service (migrations will auto-run on first start)
Verify: GET /api/v1/version should show new version
Verify: GET /api/v1/orgs/MokoConsulting/issue-statuses should return [] (empty until statuses are created)
Publish updated MCP to npm: cd mcp-mokogitea-api && npm publish

After Deploy

Create org-level status definitions (Open, In Progress, Pending Testing, Complete, etc.)
Create org-level priority definitions (P0-Critical, P1-High, P2-Medium, P3-Low)
Create org-level type definitions (Feature, Bug, Enhancement, Test, Documentation, Chore, Roadmap)
Bulk-set status/priority/type on all MokoSuite issues (~148 issues across 8 repos)

Current State

PR #591: merged ✓
Server binary: OLD (still running pre-merge version)
API endpoints: returning 404
MCP config: updated to npx ✓

## Summary PR #591 merged to main. The new binary needs to be built and deployed to enable the issue metadata API endpoints. ## What Was Merged - First-class `status_id`, `priority_id`, `type_id` fields on issues - Org-level definition endpoints: `/orgs/{org}/issue-statuses`, `/issue-priorities`, `/issue-types` - Issue JSON includes `status_name`, `priority_name`, `type_name` resolved from IDs - PATCH/POST on issues accepts `status_id`, `priority_id`, `type_id` - Migration v355 for manifest metadata fields - Org wiki tab with internal/external mode ## Deploy Steps 1. Build MokoGitea-APP from `main` branch (`make build` or `go build`) 2. Stop the running Gitea service 3. Replace the binary 4. Start the service (migrations will auto-run on first start) 5. Verify: `GET /api/v1/version` should show new version 6. Verify: `GET /api/v1/orgs/MokoConsulting/issue-statuses` should return `[]` (empty until statuses are created) 7. Publish updated MCP to npm: `cd mcp-mokogitea-api && npm publish` ## After Deploy - Create org-level status definitions (Open, In Progress, Pending Testing, Complete, etc.) - Create org-level priority definitions (P0-Critical, P1-High, P2-Medium, P3-Low) - Create org-level type definitions (Feature, Bug, Enhancement, Test, Documentation, Chore, Roadmap) - Bulk-set status/priority/type on all MokoSuite issues (~148 issues across 8 repos) ## Current State - PR #591: merged ✓ - Server binary: OLD (still running pre-merge version) - API endpoints: returning 404 - MCP config: updated to npx ✓

jmiller commented

2026-06-09 21:11:51 +00:00

Branch created: feature/596-deploy-issue-metadata-api-status-priorit

git fetch origin
git checkout feature/596-deploy-issue-metadata-api-status-priorit

Branch created: [`feature/596-deploy-issue-metadata-api-status-priorit`](https://code.mokoconsulting.tech/MokoConsulting/MokoGitea-APP/src/branch/feature/596-deploy-issue-metadata-api-status-priorit) ```bash git fetch origin git checkout feature/596-deploy-issue-metadata-api-status-priorit ```

Sign in to join this conversation.

Priority -

Type -

Status —

Priority —

Type —

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGitea-APP#596