Items query is now returning items in order of id, rather than board position

monday Apps & Developers
,
1

It seems as though the API is now returning items/subitems in order of ID ascending, rather than by their board position (Main Table). This is true even when using old API versions.

Is this intentional? It has broken several use cases for me, as I use the board order to express information.

If it is intentional, has it been announced anywhere? Can we change this via an argument? Please help!

Board (Main Table):

Screenshot 2024-12-21 at 21.53.06
Screenshot 2024-12-21 at 21.53.06936Ă—844 34.4 KB

Query:

  boards(ids: 6774044620){
    items_page (limit: 50){
      items {
        id 
        name
        subitems{
          id
          name
        }
      }
    }
  }
}

Response:

Screenshot 2024-12-21 at 21.52.03
Screenshot 2024-12-21 at 21.52.03670Ă—1012 71.2 KB

2

Hello there @FrancisElliott,

On a small test I did I can see that if the board has items and subitems, the items come in the same order as you see them in the UI. The subitems are coming as “oldest first”. Are you saying that before you got the subitems in the same order as they were shown in each item via the UI?

Looking forward to hearing from you!

Cheers,
Matias

3

That is correct. The subitems were returning in the order they were shown in the UI. This was the standard behavior for items and subitems. It appears to have changed.

4

Hello again,

Matias here!

Thank you for that confirmation!

As far as I can see, that is still the case for items. I will check with the team about the subitems and let you know what they say!

Cheers,
Matias

6

@Matias.Monday Having done some more digging, it appears that this change was made between the 14th and 17th of December. I can see this response on the 14th December still demonstrating the original behavior of returning subitems in the order they appear in the UI.

Screenshot 2024-12-23 at 11.00.07
Screenshot 2024-12-23 at 11.00.07868Ă—1660 192 KB

8

Hello again @FrancisElliott ,

Thank you for that information!

I checked with our team and this will be fixed in the upcoming days, reverting the change you mention :smile:

1 Like
9

Thank you @Matias.Monday!

10

Happy to help @FrancisElliott !

11

@Matias.Monday Thanks for all the help. Please let us know once this is fixed. Happy new year!

12

@Matias.Monday Just confirming that this issue remains ongoing.

13

Hello there @FrancisElliott,

I heard back from the team and they mentioned that this should be resolved by the end of this week :smile:

1 Like
14

Hello everyone!

A fix has been deployed for this :smile:

15

Looks to be working correctly! :+1:

16

I am glad that is the case!