rest/agile/1.0 API: Timeout on `/board/<>/project` but `/board/<>/project/full` get empty

[First]

Hi there,

Does anyone here experience the weird behavior related to the `rest/agile/1.0/board/<>` API?

• When we fetch `/rest/agile/1.0/board/<boardId>` we get the `location.projectId` correctly.
• We experience that when we fetch `/rest/agile/1.0/board/<boardId>/project?startAt=0&maxResults=50` and it's always timeout.
• While we fetch with  `/rest/agile/1.0/board/<boardId>/project/full` we get `{ maxResults: 50, startAt: 0, total: 0, isLast: true, values: [ [length]: 0 ] }`

You can see that there is actually the board location, which is the Project, but when I try to get the project associated with the boards, it's timeouts or returns nothing.

[Sunny Ape · Accepted solution]

Hello @First 

I cannot replicate that problem.

For me, both the Get Projects and Get Projects full endpoints are working exactly as expected and as described in the documentation.

If you do a GET request to:

/rest/agile/1.0/board/<boardId>/project

and don't supply the startAt or maxResults parameters, does the request still timeout?

Also, in the response you got from request to:

/rest/agile/1.0/board/<boardId>/project/full

I can see it returned total: 0, which means that the Board is located on a Project but it isn't associated with any Project(s). That's because the Board's filter doesn't contain any references to any Project(s), which is described in that API endpoint's documentation:

A project is associated with a board if the board filter contains a reference to the project

A Board that uses a filter that isn't associated with any specific Project(s) essentially becomes associated with ALL projects, so a request to the Get Projects endpoint would result in a search against every single Project in the entire organisation, which is potentially a massive undertaking that cannot be completed within the request time limit, hence the timeout.

If someone in your organisation has created a Board with such an unconstrained filter, they have essentially created a monster! Boards really should be limited to displaying issues from not more than 50 projects before their performance starts to degrade noticeably.

[Marc - Devoteam]

Hi @First 

Same here as mentioned by @Sunny Ape no issues encountered, endoints work as expected

Curious though, why do you want to use the params startAt en maxResults on call /rest/agile/1.0/board/<boardId>/project

Do you have more then 50 project issues form different projects in a single board?