You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tasks have a field sort_order which is used to order fields (from low to high). When adding new tasks, a sort_order should be given.
Presumably, new tasks would appear at the and of a column, if tasks already exist. This means that cards that are added, the "highest sort order" should be retrieved from the database; new tasks have to be given a sort order that is higher than that.
Practical example:
task1 in todo: sort_order = 10
task2 in todo: sort_order = 20
new task(3) to be inserted in todo: 20 + (default sort order increment, can be 1 or higher)
Currently, tasks are added with the creation of a new project with a "loop id" (from 1 to X). This should be changed to "highest value of last card in column" + "loop id".
Next steps:
perform research on examples on how to sort tasks. How does this work in other systems? nosql?
We suggest to research this ticket and time-box this on 2 days.
The text was updated successfully, but these errors were encountered:
Tasks have a field sort_order which is used to order fields (from low to high). When adding new tasks, a sort_order should be given.
Presumably, new tasks would appear at the and of a column, if tasks already exist. This means that cards that are added, the "highest sort order" should be retrieved from the database; new tasks have to be given a sort order that is higher than that.
Practical example:
task1 in todo: sort_order = 10
task2 in todo: sort_order = 20
new task(3) to be inserted in todo: 20 + (default sort order increment, can be 1 or higher)
Currently, tasks are added with the creation of a new project with a "loop id" (from 1 to X). This should be changed to "highest value of last card in column" + "loop id".
Next steps:
We suggest to research this ticket and time-box this on 2 days.
The text was updated successfully, but these errors were encountered: