mirror of
https://github.com/go-vikunja/vikunja.git
synced 2026-03-09 07:13:35 -05:00
Task is not visible in Overview or in Project view even if it belongs to the project #556
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dgliwka on GitHub (Aug 19, 2025).
Description
Tasks with number >118 are not visible in overview and in any (list, Gantt, table, Kanban) view of the project.
Only possibility to see such task is to use URL of
/tasks/119.I am not using any filters.
Tasks are created using "Add task" bar. Tasks are similar to existing ones.
Vikunja Version
v1.0.0-rc1
Browser and version
Vivaldi 7.4.3671.3
Can you reproduce the bug on the Vikunja demo site?
No
Screenshots
@kolaente commented on GitHub (Aug 19, 2025):
Are you able to find it when going through the task pages manually? Or does it not appear at all?
@dgliwka commented on GitHub (Aug 19, 2025):
It does not appear at all in any of the lists and views.
@kolaente commented on GitHub (Aug 20, 2025):
Seems to be a bug then - not sure how to reproduce this.
@kolaente commented on GitHub (Sep 1, 2025):
Does it appear when you create a new view in a project? Do new tasks appear?
@dgliwka commented on GitHub (Sep 1, 2025):
No, after creating new view (tested for list view) in a project, some of the tasks do not appear.
@kolaente commented on GitHub (Sep 1, 2025):
Do you see pagination buttons on the bottom of the page? Do new tasks you create in other projects appear in these other projects?
@dgliwka commented on GitHub (Sep 2, 2025):
I do see pagination buttons. Tasks with # > 118 do not show on any of these pages.
Tasks with # > 118 AND starred appear in the "Favorite" list.
Tasks with # > 118 created in other projects appear in these projects views and in "Overview" view correctly.
Seems something is wrong with this particular project only and it's views.
@kolaente commented on GitHub (Sep 2, 2025):
Are you using typesense?
@dgliwka commented on GitHub (Sep 2, 2025):
Yes I did. Disabling typesense solved the problem