The current implementation uses a lot of subqueries, which causes unnecessary server load
Proposal
kanban(){} graphql resolver similar to inbox that would collect tasks and necessary data to display the kanban using optimized SQL query / queries.
KanBanNode {
id # task id
name # task name
label # task label
status # task status
tags # task tags
taskType
assignees
updatedAt # task.updated_at
createdAt # task.created_at
dueDate # task.attrib.endDate
folderId
folderName
folderLabel
folderPath
thumbnailId # task.thumbnal_id
lastVersionWithThumbnailId # id of the last version having thumbnail
}
Story
Problems
The current implementation uses a lot of subqueries, which causes unnecessary server load
Proposal
kanban(){}
graphql resolver similar toinbox
that would collect tasks and necessary data to display the kanban using optimized SQL query / queries.