Skip to content

feat(api): expose issue sorting in project column listings - #39145

Open
lunny wants to merge 2 commits into
go-gitea:mainfrom
lunny:lunny/project-column-issue-sorting
Open

feat(api): expose issue sorting in project column listings#39145
lunny wants to merge 2 commits into
go-gitea:mainfrom
lunny:lunny/project-column-issue-sorting

Conversation

@lunny

@lunny lunny commented Aug 26, 2026

Copy link
Copy Markdown
Member

The project column issue listing returned plain issues, so the kanban order was only implicit in the response order and clients had no value to feed back into the move endpoint.

Each item now carries an extra sorting key next to the inlined issue fields, which makes the board order readable and repositioning deterministic for external tooling. The wire format stays a superset of the previous one, so clients decoding plain issues are unaffected.

Fixes: #37151

Assisted-by: Codet:claude-sonnet-4.5

Returns each issue in a project column together with its sorting value,
so clients can read the board order and compute positions for the move
endpoint.

Fixes: go-gitea#37151

Assisted-by: Codet:claude-sonnet-4.5
@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Aug 26, 2026
@github-actions github-actions Bot added topic/api Concerns mainly the API type/feature Completely new functionality. Can only be merged if feature freeze is not active. labels Aug 26, 2026
Keeps the response items shaped like plain issues with an extra sorting
key, so clients that decode issues from this endpoint are unaffected.

Assisted-by: Codet:claude-sonnet-4.5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. topic/api Concerns mainly the API type/feature Completely new functionality. Can only be merged if feature freeze is not active.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Expose kanban issue ordering via API (critical for working with agentic workflows)

2 participants