github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 11:37:49 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

list and table views do not show (sub)tasks if the parent task is in anothe project #2228

New Issue
Closed
opened 2026-03-22 13:58:16 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-03-22 13:58:16 -05:00
Owner
Copy Link

Originally created by @avatar1024 on GitHub (May 15, 2025).

Description

If I move subtask from the project where the parent task is to another project, the subtask appears in the kaban and gantt views of that other project but not in the list or table view. It however still (usefully) remains in the list and table view of the original project where the parent task is.

I would expect (and it would be good) that the task appear in all views of the project it has been moved to (but I'd say it makes sense if it also stays in the list view of the project the parent task is). It is for example essential so that we can easily keep track and manage task with many subtasks, and overall create more consistent hierarchies and progress tracking between projects, sub-projects, tasks and subtasks.

For more on the topic of small inconsistencies I encountered in Vikunja in the logic and managements of the hierarchy between project/subprojects/tasks/subtasks, I finally found the time to write a little piece here: https://community.vikunja.io/t/improvement-suggestions/3732.

Vikunja Version

0.24.6

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

Image
Image
Image
Image
Image

Originally created by @avatar1024 on GitHub (May 15, 2025). ### Description If I move subtask from the project where the parent task is to another project, the subtask appears in the kaban and gantt views of that other project but not in the list or table view. It however still (usefully) remains in the list and table view of the original project where the parent task is. I would expect (and it would be good) that the task appear in all views of the project it has been moved to (but I'd say it makes sense if it also stays in the list view of the project the parent task is). It is for example essential so that we can easily keep track and manage task with many subtasks, and overall create more consistent hierarchies and progress tracking between projects, sub-projects, tasks and subtasks. For more on the topic of small inconsistencies I encountered in Vikunja in the logic and managements of the hierarchy between project/subprojects/tasks/subtasks, I finally found the time to write a little piece here: https://community.vikunja.io/t/improvement-suggestions/3732. ### Vikunja Version 0.24.6 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots ![Image](https://github.com/user-attachments/assets/282be8d5-a35f-4c11-b8ce-727a421fe566) ![Image](https://github.com/user-attachments/assets/1456ee73-6e6d-47ad-a696-1d224b1d0bdc) ![Image](https://github.com/user-attachments/assets/34368176-fb11-489c-a884-4926d8003f2b) ![Image](https://github.com/user-attachments/assets/549a6637-eb10-40fa-abf6-d4487692db21) ![Image](https://github.com/user-attachments/assets/d6178232-7e23-4e67-b367-255f92f2f5ed)
GiteaMirror commented 2026-03-22 13:58:16 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (May 16, 2025):

Do you see this only with subtasks or with no-related tasks as well?

@kolaente commented on GitHub (May 16, 2025): Do you see this only with subtasks or with no-related tasks as well?
GiteaMirror commented 2026-03-22 13:58:17 -05:00
Author
Owner
Copy Link

@avatar1024 commented on GitHub (May 16, 2025):

Do you see this only with subtasks or with no-related tasks as well?

I can this happening only where there is a Parent-Subtask relation. I tried other relations and I can see no issues there. I reckon this is because only the Parent-Subtask relation has an impact on the list view, where the subtask is showed with an indent below the parent tasks in the list view of the project where the parent task lives.

When moving a subtask in another project, the in the list view of the project where the parent task lives, the subtask appears showing the name of the other project. I reckon the best would actually be to see exactly the same (both parent and subtask) int he list view of the project where the subtask lives, but this time showing the parent task with the name of the project it lives in.

@avatar1024 commented on GitHub (May 16, 2025): > Do you see this only with subtasks or with no-related tasks as well? I can this happening only where there is a Parent-Subtask relation. I tried other relations and I can see no issues there. I reckon this is because only the Parent-Subtask relation has an impact on the list view, where the subtask is showed with an indent below the parent tasks in the list view of the project where the parent task lives. When moving a subtask in another project, the in the list view of the project where the parent task lives, the subtask appears showing the name of the other project. I reckon the best would actually be to see exactly the same (both parent and subtask) int he list view of the project where the subtask lives, but this time showing the parent task with the name of the project it lives in.
GiteaMirror commented 2026-03-22 13:58:17 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jun 24, 2025):

Maybe fixed in https://github.com/go-vikunja/vikunja/pull/1000, please check with the next unstable build (should be ready for deployment in ~30min, also on try).

@kolaente commented on GitHub (Jun 24, 2025): Maybe fixed in https://github.com/go-vikunja/vikunja/pull/1000, please check with the next unstable build (should be ready for deployment in ~30min, also on [try](https://try.vikunja.io)).
GiteaMirror commented 2026-03-22 13:58:17 -05:00
Author
Owner
Copy Link

@lithiumsulfate commented on GitHub (Oct 13, 2025):

I think this is still (partially) happening in 1.0.0-rc2 (reproducible in the current demo site as well). If there are two tasks -- one in Project A and one in Project B -- and I assign the Project B task as a subtask of the one in Project A, the now-subtask will suddenly disappear from the List view of Project B (but it does still show in the Table and Kanban views of Project B).

This happens to deeper nested levels as well; the complete task tree is properly shown in the List view of the project with the highest level parent task, but none of the other project(s) List view(s) show any of the subtasks any longer.

@lithiumsulfate commented on GitHub (Oct 13, 2025): I think this is still (partially) happening in 1.0.0-rc2 (reproducible in the current demo site as well). If there are two tasks -- one in Project A and one in Project B -- and I assign the Project B task as a subtask of the one in Project A, the now-subtask will suddenly disappear from the List view of Project B (but it does still show in the Table and Kanban views of Project B). This happens to deeper nested levels as well; the complete task tree is properly shown in the List view of the project with the highest level parent task, but none of the other project(s) List view(s) show any of the subtasks any longer.
GiteaMirror commented 2026-03-22 13:58:17 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Oct 13, 2025):

@lithiumsulfate I've pushed another fix for this in https://github.com/go-vikunja/vikunja/issues/782, please check with the next unstable build (should be ready for deployment in ~30min, also on try).

@kolaente commented on GitHub (Oct 13, 2025): @lithiumsulfate I've pushed another fix for this in https://github.com/go-vikunja/vikunja/issues/782, please check with the next unstable build (should be ready for deployment in ~30min, also on [try](https://try.vikunja.io)).
GiteaMirror commented 2026-03-22 13:58:18 -05:00
Author
Owner
Copy Link

@lithiumsulfate commented on GitHub (Oct 14, 2025):

@kolaente looks good now as far as I can tell, thanks for the quick response!

@lithiumsulfate commented on GitHub (Oct 14, 2025): @kolaente looks good now as far as I can tell, thanks for the quick response!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#2228
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?