-
Suggestion
-
Resolution: Unresolved
-
955
-
35
-
Hi everyone,
I'm Yousef Abusamak, a Product Manager on the Jira team. I appreciate the ongoing interest and engagement in this request. We recognize that this API is frequently requested, with considerable votes and watchers highlighting its importance.
We will be moving this issue to be under consideration. While we haven’t committed to delivering this yet, we’re actively evaluating how it fits into our roadmap. Your feedback is invaluable in shaping our priorities, and we’ll continue to assess how we can best address this need.
I’ll share any updates as soon as we have more to communicate. Thanks for your patience and for being part of our community!
Best,
Yousef
Problem Description
At the moment, we have endpoints to view board settings. ie
- Get board settings: GET /rest/agile/1.0/board/{boardId}
- Get board property: GET /rest/agile/1.0/board/{boardId}/properties/{propertyKey}
- Full listing of board public APIs: https://developer.atlassian.com/cloud/jira/software/rest/api-group-board/#api-group-board
However, there is no public endpoint in Cloud to allow for board configuration mutation. Ie, update the Board Administrator field via rest API, configure swimlanes or specify the columns of a board
Solution
Allow for the possibility, ie via API endpoint, to perform board configuration updates.
Workaround
No workaround available
Original Description
The Jira Software REST API doesn't allow the columns of a board to be specified or configuring swimlanes when creating a board. It also doesn't allow the columns of an existing board to be updated/modified. It is suggested that the API be expanded to include these features.
- is duplicated by
-
JRACLOUD-91202 Ability to update board configuration via Rest API
- Closed
- is related to
-
ENT-2547 Failed to load
[JSWCLOUD-20535] Add the ability to define board configuration through the REST API
All comments
Pinned by
Yousef Abusamak
Hi everyone,
I'm Yousef Abusamak, a Product Manager on the Jira team. I appreciate the ongoing interest and engagement in this request. We recognize that this API is frequently requested, with considerable votes and watchers highlighting its importance.
We will be moving this issue to be under consideration. While we haven’t committed to delivering this yet, we’re actively evaluating how it fits into our roadmap. Your feedback is invaluable in shaping our priorities, and we’ll continue to assess how we can best address this need.
I’ll share any updates as soon as we have more to communicate. Thanks for your patience and for being part of our community!
Best,
Yousef