feat(issues): standard status presets and cross-org status migration #507

New Issue

2026-06-06T14:43:57Z

jmiller commented

2026-06-06 14:43:57 +00:00

Summary

Extend the custom issue statuses feature (#502) with:

1. Standard Status Presets

Provide a set of standard status definitions that new organizations get by default:

Status	Color	Closes Issue	Description
In Progress	Blue	No	Work is actively being done
Needs Info	Yellow	No	Waiting for more information
Blocked	Red	No	Cannot proceed due to external dependency
Won't Fix	Gray	Yes	Decided not to address
Duplicate	Purple	Yes	Already tracked elsewhere
Resolved	Green	Yes	Fix implemented and verified

Orgs can customize, add, remove, or reorder these. The presets are just a starting point.

2. Status Migration Between Orgs

When moving repos between organizations or forking, provide a way to:

Map source org statuses to target org statuses
Create missing statuses in the target org
Preserve issue status assignments during transfer

3. Status in Issue List Filters

Add a status filter to the issue list page (alongside label, milestone, assignee filters) so users can filter issues by custom status.

4. Status in Issue API

Expose status on the issue API:

returns object
accepts to set status
lists available statuses

Motivation

Custom statuses (#502) are currently org-specific with no defaults. New orgs start with zero statuses and must configure everything manually. Standard presets reduce setup friction. The filter and API support make statuses useful at scale.

Authored by Jonathan Miller (@jmiller)

## Summary Extend the custom issue statuses feature (#502) with: ### 1. Standard Status Presets Provide a set of standard status definitions that new organizations get by default: | Status | Color | Closes Issue | Description | |--------|-------|:---:|---| | In Progress | Blue | No | Work is actively being done | | Needs Info | Yellow | No | Waiting for more information | | Blocked | Red | No | Cannot proceed due to external dependency | | Won't Fix | Gray | Yes | Decided not to address | | Duplicate | Purple | Yes | Already tracked elsewhere | | Resolved | Green | Yes | Fix implemented and verified | Orgs can customize, add, remove, or reorder these. The presets are just a starting point. ### 2. Status Migration Between Orgs When moving repos between organizations or forking, provide a way to: - Map source org statuses to target org statuses - Create missing statuses in the target org - Preserve issue status assignments during transfer ### 3. Status in Issue List Filters Add a status filter to the issue list page (alongside label, milestone, assignee filters) so users can filter issues by custom status. ### 4. Status in Issue API Expose status on the issue API: - returns object - accepts to set status - lists available statuses ## Motivation Custom statuses (#502) are currently org-specific with no defaults. New orgs start with zero statuses and must configure everything manually. Standard presets reduce setup friction. The filter and API support make statuses useful at scale. --- *Authored by Jonathan Miller (@jmiller)*

Sign in to join this conversation.

Priority Medium

Type Feature

Status —

Priority —

Type —

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGitea-APP#507