MokoConsulting/MokoGitea-Fork
1
0
Fork 0
Code Issues 162 Pull Requests Releases 96 Wiki Activity

test: issue status system — required baseline statuses #686

New Issue
Open
opened 2026-06-21 23:04:43 +00:00 by jmiller · 0 comments
jmiller commented 2026-06-21 23:04:43 +00:00
Owner
Copy Link
Copy Source

Parent: #683

Issue Status Tests (#681)

Seeding

  • Existing org (MokoConsulting): check if statuses need manual seed (existing orgs predate this change)
  • Create new test org → verify 6 statuses auto-seeded: Open, In Progress, Waiting, In Review, Closed, Won't Fix
  • Open and Closed have is_required: true

Delete Protection

  • Try to delete Open status → verify error flash: 'Cannot delete required status'
  • Try to delete Closed status → same protection
  • Delete a non-required status (e.g., Waiting) → should succeed
  • Lock icon visible on required statuses in the settings table
  • Delete button hidden for required statuses (replaced by disabled lock icon)

API

  • GET /api/v1/orgs/MokoConsulting/issue-statuses → JSON includes is_required field
  • Required statuses show is_required: true
  • Custom statuses show is_required: false

Rename

  • Rename a required status (e.g., Won't Fix → Not Planned) → should succeed
  • Rename Open or Closed → should succeed (renaming allowed, deleting blocked)
Parent: #683 ## Issue Status Tests (#681) ### Seeding - [ ] Existing org (MokoConsulting): check if statuses need manual seed (existing orgs predate this change) - [ ] Create new test org → verify 6 statuses auto-seeded: Open, In Progress, Waiting, In Review, Closed, Won't Fix - [ ] Open and Closed have `is_required: true` ### Delete Protection - [ ] Try to delete Open status → verify error flash: 'Cannot delete required status' - [ ] Try to delete Closed status → same protection - [ ] Delete a non-required status (e.g., Waiting) → should succeed - [ ] Lock icon visible on required statuses in the settings table - [ ] Delete button hidden for required statuses (replaced by disabled lock icon) ### API - [ ] `GET /api/v1/orgs/MokoConsulting/issue-statuses` → JSON includes `is_required` field - [ ] Required statuses show `is_required: true` - [ ] Custom statuses show `is_required: false` ### Rename - [ ] Rename a required status (e.g., Won't Fix → Not Planned) → should succeed - [ ] Rename Open or Closed → should succeed (renaming allowed, deleting blocked)
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
 feature: wiki
Wiki system enhancements
 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-Fork#686
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?