Regression: Task sorting not working when tasks created in webui and tasks.org

Open
#3,292 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
54/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, mariadb, php
Domain
backend, databases

Research direction

Start by tracing the creation date and last modified sorting paths in the Tasks app, then compare how WebUI-created and Android-created tasks are represented. Reproduce with mixed-source tasks and inspect the sort values; done when both sorting options order those tasks by the requested dates.

Written by the indexing model from the issue text.

Description

bug
Steps to reproduce
  1. Create multiple tasks in the WebUI and in the Android tasks.org app so that creation times are mixed
  2. Sort tasks by creation date / last modified
  3. None of the sorting variants really sort by creation or last modified. Instead they are somehow grouped together by the source app they were created with and "a little bit" by creation / modified date

In previous versions it was working correctly.

Expected behavior

Sort tasks correctly by creation / modified date.

Actual behaviour

Sorting is scrambled.

Tasks app version

0.18.1

CalDAV-clients used

DAVx5

Browser

Latest Firefox

Client operating system

Linux

Server operating system

Ubuntu

Web server

Apache

Database engine version

MariaDB

PHP engine version

PHP 8.0

Nextcloud version

35.0.1

Updated from an older installed version or fresh install

Updated from an older version

List of activated apps

Nextcloud configuration

Web server error log

Log file

Browser log

Additional info

No response

Dominant language
JavaScript
Stars
710
Forks
125
Avg merge
19h 37m
Merged PRs (30d)
12

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nextcloud/tasks

All issues in nextcloud/tasks

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.