feat(api): expose issue sorting in project column listings - #39145
Open
lunny wants to merge 2 commits into
Open
Conversation
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
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
sortingkey 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