Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug / Feature: determine correct sort order for new tasks #123

Closed
berrydenhartog opened this issue Aug 7, 2024 · 2 comments
Closed

Bug / Feature: determine correct sort order for new tasks #123

berrydenhartog opened this issue Aug 7, 2024 · 2 comments
Labels
bug Something isn't working Stale

Comments

@berrydenhartog
Copy link
Member

berrydenhartog commented Aug 7, 2024

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.

@berrydenhartog berrydenhartog converted this from a draft issue Aug 7, 2024
@berrydenhartog berrydenhartog added bug Something isn't working and removed bug Something isn't working labels Aug 7, 2024
Copy link
Contributor

This issue did not have any activity in the last 90 days and will be removed after 30 days

@github-actions github-actions bot added the Stale label Nov 12, 2024
Copy link
Contributor

This issue is closed due to inactivity

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 12, 2024
@github-project-automation github-project-automation bot moved this from ♻ To Do to ✅ Done in 👾 AI Validation Team Planning Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Stale
Projects
Status: ✅ Done
Development

No branches or pull requests

1 participant