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

feat(issues): org-level priority field (#509) #516

Merged
jmiller merged 1 commits from feat/509-issue-priority into dev 2026-06-06 16:54:02 +00:00
Conversation 0 Commits 1 Files Changed 13
+443
jmiller commented 2026-06-06 16:53:50 +00:00
Owner
Copy Link
Copy Source

Org-level issue priorities with sidebar dropdown. Same pattern as statuses.

Closes #509

Authored by Jonathan Miller (@jmiller)

Org-level issue priorities with sidebar dropdown. Same pattern as statuses. Closes #509 --- *Authored by Jonathan Miller (@jmiller)*
jmiller added 1 commit 2026-06-06 16:53:51 +00:00
feat(issues): org-level priority field with customizable levels (#509)
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
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
Generic: Repo Health / Site Health (pull_request) Has been skipped
Details
Branch Policy Check / Verify merge target (pull_request) Successful in 1s
Details
Generic: Repo Health / Access control (pull_request) Successful in 2s
Details
PR RC Release / Build RC Release (pull_request) Successful in 2s
Details
Branch Cleanup / Delete merged branch (pull_request) Successful in 1s
Details
Universal: Pre-Release / Build Pre-Release (${{ inputs.stability || 'development' }}) (pull_request) Failing after 30s
Details
55c2f81c58 
Add org-level issue priority definitions that appear in the issue
sidebar. Each priority has a name, color, sort order, and optional
default flag. Follows the same architecture as custom statuses (#502).

Includes:
- IssuePriorityDef model with CRUD operations
- Migration v348 adding issue_priority_def table + priority_id on issues
- Org settings UI for managing priorities
- Issue sidebar dropdown for selecting priority

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
jmiller merged commit 759a8f590c into dev 2026-06-06 16:54:02 +00:00
jmiller deleted branch feat/509-issue-priority 2026-06-06 16:54:02 +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#516
Delete Branch "feat/509-issue-priority"

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?