Jira Software Cloud "Get issues for board" REST API does not return the correct issues for boards of next-gen projects

Jira Development Jira Cloud
,
1

Hi,

Has anyone experienced the following problem?

Steps to reproduce the bug

  1. Create a new next-gen type project
  2. Turn on the “Backlog” at the project features, but don’t turn on the “Sprints”
  3. Create 3 issues in the backlog
  4. Add only the first issue to the board (let’s say its id is 2)
  5. Call this REST API endpoint: https://<JIRA_BASE_URL>/rest/agile/1.0/board/2/issue

https://developer.atlassian.com/cloud/jira/software/rest/#api-rest-agile-1-0-board-boardId-issue-get

Expected Result

JSON result contains only the first issue.

Actual Result

JSON result contains all 3 issues.

Regards,
Ferenc

2

I don’t think it’s necessary a bug but rather a missing feature. The /issue end point is supposed to get all of the issues associated with the board (the issues in the backlog are in the board). What’s missing is a /not-in-the-backlog since there is a /backlog end point.

Not sure where one would drop in feature requests for Jira nowadays though.

1 Like
3

We tried to use the following logic: get issues for board (https://developer.atlassian.com/cloud/jira/software/rest/#api-rest-agile-1-0-board-boardId-issue-get) and subtract the issues for backlog (https://developer.atlassian.com/cloud/jira/software/rest/#api-rest-agile-1-0-board-boardId-backlog-get).

This seemed to work, but found a case when it does not.

https://<my_jira_base_url>/rest/agile/1.0/board/5/issue

  "expand": "schema,names",
  "startAt": 0,
  "maxResults": 50,
  "total": 4,
  "issues": [...]

next-gen-board
next-gen-board1903×898 32.7 KB

https://<my_jira_base_url>/rest/agile/1.0/board/5/backlog

"expand": "schema,names",
  "startAt": 0,
  "maxResults": 50,
  "total": 3,
  "issues": [...]

next-gen-backlog
next-gen-backlog1903×947 37.7 KB

The backlog enpoint does not return the NG2-2 issue, which is resolved, but visible in the Backlog screen.

All of this is quite confusing, and really seemes to be a bug in the backlog endpoint.

4

I was able to replicate this. Discussing with the team if this is the intended behaviour.

5

@aagrawal2 Do you have any updates?
We have released the new version of our app yesterday, but this feature couldn’t be added. The next version comes in weeks, and we would love to add this feature to that release.

6

@aron.gombas @ferenc.nagy

I just confirmed with our team and it is a missing feature. I have created a feature request for you guys which you can follow up here - Jira Service Management.

Feel free to raise a ticket for a feature request or suggestion in the future via this link in our portal.

Cheers,
Anmol

7

I cannot open the URL: Jira Service Management
It says, “You do not have permission to view this request.”.

8

Here is the public ticket - [JSWCLOUD-21514] Jira Software Cloud “Get issues for board” REST API does not return the correct issues for boards of next-gen projects - Create and track feature requests for Atlassian products.
Please ignore the previous one.

9

@aagrawal2, Hi Anmol. It’s Tania from Planyway. Our team’s faced a similar issue with the next-gen project. We’re currently updating Planyway and plan to load issues separately, from the board and from the backlog to Planyway. When there’s a lot of issues in the backlog, Planyway takes long to load, and that’s because it’s loading the whole backlog together with the board. We were wondering if that’d be possible to not load issues from the backlog when the board is loading. It seems that the suggestion posted in this thread is exactly what we need, but there was no news for 2 year. Could you give us an update on this, perhaps?

11

@aagrawal2

Any update on this? It is still not possible to correctly get the issues of a team-managed Kanban board for users.

I’m currently advising my users against using team-managed projects for this reason.

1 Like
12

@PeterJuras @Tania Let me check in with our team to get latest update on this.