In the 2023-07 version:
query { boards(ids: 1234567890) { items { name column _ values { title text } } } }
In the 2023-10 version, however, all that remains is to return the information in the columns
query { boards(ids: 1234567890) { items_page(limit:100) { cursor items { id name }}}}
Adding Column values ?
This doesn’t work anymore but it’s still in the documentation
Column values
this appears to be a typo/error. Just user column_values like in the old version, they didn’t change the text used for that subquery.
BUT there are many changes for column_values v2. notably that mirror columns (and connect board columns, and dependency columns do not return text values anymore and require to use the fragments inside column_values (here is a snipped that shows the ... on MirrorValue fragment inside the column_values. BoardRelationValue and DependencyValue are used for the others.
column_value {
... on MirrorValue {
display_value
}
}
As always your best bet is to play around in the playground to see how things work.
I’m not sure what it would look like in version 2023-10
query { boards(ids: 1234567890) { items_page(limit:100) { cursor items { id name }}}}
How do I put Column values in the request, in version 2023-10
Don’t look at documentation examples as a LIMIT of what’s possible, they are a STARTING POINT. GraphQL you just add in the stuff you want, its descriptive, not prescriptive. If you need something more, just add it in. Use the API playground to explore what’s permitted.
Since column values are a part of an item, you would include it within items, items are part of boards so they go inside boards. (Though you can access items directly if you know the IDs). You just need items_page for items in a board (the assumption being you DON’T know any item IDs, there is no point using boards if you know item IDs)
{
boards(ids: "1234567890") {
items_page(limit: 100) {
cursor
items {
id
name
column_values(ids: ["column_id1", "column_id2"]) {
id
type
text
value
... on MirrorValue {
display_value
}
... on BoardRelationValue {
display_value
}
... on DependencyValue {
display_value
}
}
}
}
}
}
You only need to include the GraphQL fragments if you’re getting those types AND you want the display_value (previously returned as text). But explore them, every type can return additional details you couldn’t get before.
... on NumbersValue {
number
}
Number now an actual number value, not a string.