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

feat(issues): org-level priority field with customizable levels #509

New Issue
Closed
opened 2026-06-06 14:45:48 +00:00 by jmiller · 1 comment
jmiller commented 2026-06-06 14:45:48 +00:00
Owner
Copy Link
Copy Source

Summary

Add a first-class Priority field for issues, following the same org-level definition pattern as custom issue statuses (#502). Priorities are defined at the organization level and appear in the issue sidebar for all repos.

Design

Priority Definition (Org Settings)

Org admins define priority levels in Org Settings > Issue Priorities:

Field Description
Name Priority level name (e.g., Critical, High, Medium, Low)
Color Hex color for visual distinction
Icon Optional icon identifier
Sort Order Display priority (lower = higher priority)
Is Default Whether this priority is auto-assigned to new issues
SLA Hours Optional SLA target in hours for response/resolution

Default Presets

New organizations get these presets:

Priority Color Sort SLA Hours
Critical Red 1 4
High Orange 2 24
Medium Yellow 3 72
Low Blue 4 168

Issue Sidebar

Priority dropdown appears in the issue sidebar (like status does). Auto-submits on change.

Issue List Filter

Add priority to the issue list filter bar alongside labels, milestones, assignees, and status.

API

    • list definitions
    • create definition
    • update
    • delete
  • Issue API: field on GET/PATCH

Relationship to Custom Fields

Priority is a first-class field (like status), not a custom field. This allows:

  • Dedicated database column on the issue table for efficient filtering and sorting
  • Consistent UI treatment across all orgs
  • SLA tracking tied to priority levels
  • Priority-based sorting in issue lists

Implementation

Follow the same architecture as #502 (custom statuses):

  • table for org-level definitions
  • column on the table
  • Org settings handler + template
  • Issue sidebar template
  • Priority update handler

Authored by Jonathan Miller (@jmiller)

## Summary Add a first-class **Priority** field for issues, following the same org-level definition pattern as custom issue statuses (#502). Priorities are defined at the organization level and appear in the issue sidebar for all repos. ## Design ### Priority Definition (Org Settings) Org admins define priority levels in Org Settings > Issue Priorities: | Field | Description | |-------|-------------| | Name | Priority level name (e.g., Critical, High, Medium, Low) | | Color | Hex color for visual distinction | | Icon | Optional icon identifier | | Sort Order | Display priority (lower = higher priority) | | Is Default | Whether this priority is auto-assigned to new issues | | SLA Hours | Optional SLA target in hours for response/resolution | ### Default Presets New organizations get these presets: | Priority | Color | Sort | SLA Hours | |----------|-------|:----:|:---------:| | Critical | Red | 1 | 4 | | High | Orange | 2 | 24 | | Medium | Yellow | 3 | 72 | | Low | Blue | 4 | 168 | ### Issue Sidebar Priority dropdown appears in the issue sidebar (like status does). Auto-submits on change. ### Issue List Filter Add priority to the issue list filter bar alongside labels, milestones, assignees, and status. ### API - - list definitions - - create definition - - update - - delete - Issue API: field on GET/PATCH ## Relationship to Custom Fields Priority is a **first-class field** (like status), not a custom field. This allows: - Dedicated database column on the issue table for efficient filtering and sorting - Consistent UI treatment across all orgs - SLA tracking tied to priority levels - Priority-based sorting in issue lists ## Implementation Follow the same architecture as #502 (custom statuses): - table for org-level definitions - column on the table - Org settings handler + template - Issue sidebar template - Priority update handler --- *Authored by Jonathan Miller (@jmiller)*
jmiller commented 2026-06-06 20:59:15 +00:00
Author
Owner
Copy Link
Copy Source

Testing Complete

Deployed to production (v1.26.1-moko.06.06.00+).

Test Result
Auto-seed 4 default priorities (Critical/High/Medium/Low) PASS
Priority dropdown in issue sidebar PASS
Setting priority persists PASS
Org settings page for managing priorities PASS
Default badge on Medium priority PASS
Bulk priority migration for 622 open issues PASS

Authored by Jonathan Miller (@jmiller)

## Testing Complete Deployed to production (v1.26.1-moko.06.06.00+). | Test | Result | |------|--------| | Auto-seed 4 default priorities (Critical/High/Medium/Low) | PASS | | Priority dropdown in issue sidebar | PASS | | Setting priority persists | PASS | | Org settings page for managing priorities | PASS | | Default badge on Medium priority | PASS | | Bulk priority migration for 622 open issues | PASS | --- *Authored by Jonathan Miller (@jmiller)*
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#509
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?