Loading
feat(boards): add status_id support to issue board lists
What does this MR do?
Adds support for status-based issue board lists:
CreateIssueBoardListOptions.StatusID(boards.go) andCreateGroupIssueBoardListOptions.StatusID(group_boards.go), soPOST .../boards/:board_id/listscan be called withstatus_id.- New
BoardListStatusresponse entity (id,name,icon_name,color,position,description,category) andBoardList.Statusso status lists can be read back.
Naming follows the existing BoardListAssignee precedent.
Why
gitlab-org/gitlab MR !260752 (gitlab-org/gitlab#557140 (closed)) lets clients create issue board lists by status, the fifth mutually-exclusive list type next to label, assignee, milestone, and iteration (EE-only, board_status_lists license). This unblocks gitlab-org/terraform-provider-gitlab#6569, which adds status_id to the lists block of gitlab_project_issue_board and gitlab_group_issue_board.
What does this affect
- No breaking changes: new optional request parameter
status_idand new response fieldstatus. - This MR is a draft because the GitLab MR (!260752) is still under review and the API contract may still change.
Related issues and merge requests
- gitlab-org/gitlab#557140 (closed) (upstream API)
- gitlab-org/gitlab!260752 (merged) (dependency, still open)
- gitlab-org/terraform-provider-gitlab#6569 (provider-side use case)
Checklist
-
make reviewablepasses locally (setup, generate, fmt, lint, test) - Tests cover creating status lists for project and group boards, and reading them back
Edited by Daniel Ziegenberg