MokoConsulting/MokoGitea
1
0
Fork 0
Code Issues 156 Pull Requests 2 Releases 96 Wiki Activity

feat(issues): custom status definitions with automated actions (#502) #503

Merged
jmiller merged 1 commits from feat/502-custom-issue-statuses into dev 2026-06-06 14:13:40 +00:00
Conversation 0 Commits 1 Files Changed 13
+474
jmiller commented 2026-06-06 13:43:54 +00:00
Owner
Copy Link
Copy Source

Summary

  • Add org-level custom issue status definitions (name, color, closes_issue flag)
  • Org settings UI for managing statuses at /settings/issue-statuses
  • Issue sidebar dropdown for selecting status with auto-submit
  • Automatic close/reopen when selecting a status with closes_issue=true
  • Migration v346 adding issue_status_def table + status_id on issues

Closes #502

Test Plan

  • Org settings page renders
  • Creating statuses works
  • Status dropdown in issue sidebar
  • Auto close/reopen
  • Delete status clears references

Authored by Jonathan Miller (@jmiller)

## Summary - Add org-level custom issue status definitions (name, color, closes_issue flag) - Org settings UI for managing statuses at /settings/issue-statuses - Issue sidebar dropdown for selecting status with auto-submit - Automatic close/reopen when selecting a status with closes_issue=true - Migration v346 adding issue_status_def table + status_id on issues Closes #502 ## Test Plan - [x] Org settings page renders - [x] Creating statuses works - [x] Status dropdown in issue sidebar - [ ] Auto close/reopen - [ ] Delete status clears references --- *Authored by Jonathan Miller (@jmiller)*
jmiller added 1 commit 2026-06-06 13:43:56 +00:00
feat(issues): custom status definitions with automated actions (#502)
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: Repo Health / Site Health (push) Has been skipped
Details
Generic: Repo Health / Access control (push) Successful in 1s
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
Generic: Repo Health / Scripts governance (pull_request) Blocked by required conditions
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
Branch Policy Check / Verify merge target (pull_request) Successful in 1s
Details
Generic: Repo Health / Site Health (pull_request) Has been skipped
Details
Universal: PR Check / Branch Policy (pull_request) Successful in 2s
Details
Generic: Repo Health / Access control (pull_request) Successful in 1s
Details
PR RC Release / Build RC Release (pull_request) Successful in 2s
Details
Universal: PR Check / Validate PR (pull_request) Failing after 8s
Details
Branch Cleanup / Delete merged branch (pull_request) Successful in 2s
Details
Universal: Pre-Release / Build Pre-Release (${{ inputs.stability || 'development' }}) (pull_request) Failing after 27s
Details
c568e199ed 
Add org-level custom issue status definitions that appear in the issue
sidebar. Each status has a name, color, description, and an optional
"closes issue" flag that automatically closes/reopens the issue when
the status is selected.

Includes:
- IssueStatusDef model with CRUD operations
- Migration v346 adding issue_status_def table + status_id on issues
- Org settings UI for managing statuses
- Issue sidebar dropdown for selecting status
- Auto close/reopen when status has closes_issue flag

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
jmiller merged commit 7e615516eb into dev 2026-06-06 14:13:40 +00:00
jmiller deleted branch feat/502-custom-issue-statuses 2026-06-06 14:13:40 +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 -
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#503
Delete Branch "feat/502-custom-issue-statuses"

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?