[BUG] Issue Type not editable #721

New Issue

2026-07-01T05:11:18Z

jmiller commented

2026-07-01 05:11:18 +00:00

After a issue is created the type is not editable. Type should be able to be multi select like labels, also we should be able to connect a type to a issue template like we do with labels

jmiller added the bug label 2026-07-01 05:11:18 +00:00

jmiller commented

2026-07-01 05:11:21 +00:00

Branch created: feature/721-bug-issue-type-not-editable

git fetch origin
git checkout feature/721-bug-issue-type-not-editable

Branch created: [`feature/721-bug-issue-type-not-editable`](https://git.mokoconsulting.tech/MokoConsulting/MokoGitea-Fork/src/branch/feature/721-bug-issue-type-not-editable) ```bash git fetch origin git checkout feature/721-bug-issue-type-not-editable ```

jmiller referenced this issue from a commit

2026-07-04 21:27:57 +00:00

fix: render org teams list and make issue type editable (#720, #721)

jmiller referenced this issue

2026-07-04 21:28:13 +00:00

fix: render org teams list and make issue type editable (#720, #721) #726

jmiller referenced this issue from a commit

2026-07-04 21:32:25 +00:00

Merge pull request 'fix: render org teams list and make issue type editable (#720, #721)' (#726) from fix/team-list-and-issue-type-editable into main

jmiller commented

2026-07-04 21:33:00 +00:00

The core bug — type not editable after creation — is fixed in PR #726 (merged to main).

Root cause: the type sidebar (templates/repo/issue/sidebar/issue_type.tmpl) gated its edit form on {{$canModify := and .FieldEditFlags .FieldEditFlags.CustomFields}}, but no handler ever sets FieldEditFlags → it was always nil → the type was permanently read-only. Its twin issue_priority.tmpl correctly uses HasIssuesOrPullsWritePermission; the type field now matches. Users with issue write permission get an inline dropdown that posts to the already-write-protected /issues/{id}/custom-type endpoint.

Leaving this issue open for the two remaining enhancement requests, which are separate from the bug:

Multi-select types (like labels) — currently type is single-value (type_id).
Linking a type to an issue template (like labels in template front-matter).

If preferred, I can split those into a dedicated enhancement issue and close this one.

The core bug — **type not editable after creation** — is fixed in PR #726 (merged to `main`). Root cause: the type sidebar (`templates/repo/issue/sidebar/issue_type.tmpl`) gated its edit form on `{{$canModify := and .FieldEditFlags .FieldEditFlags.CustomFields}}`, but no handler ever sets `FieldEditFlags` → it was always nil → the type was permanently read-only. Its twin `issue_priority.tmpl` correctly uses `HasIssuesOrPullsWritePermission`; the type field now matches. Users with issue write permission get an inline dropdown that posts to the already-write-protected `/issues/{id}/custom-type` endpoint. Leaving this issue **open** for the two remaining enhancement requests, which are separate from the bug: 1. Multi-select types (like labels) — currently type is single-value (`type_id`). 2. Linking a type to an issue template (like labels in template front-matter). If preferred, I can split those into a dedicated `enhancement` issue and close this one.

Sign in to join this conversation.

Priority Medium

Type Bug

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGIT#721