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

[GH-ISSUE #691] Archive parent project, children still showing but read only. #6288

New Issue
Closed
opened 2026-04-20 16:52:06 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-20 16:52:06 -05:00
Owner
Copy Link

Originally created by @key262yek on GitHub (Apr 23, 2025).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/691

Description

I have encountered an issue when archiving a parent project that contains child projects which have not been archived. Upon attempting this, I observed the following sequence:

Error Message: An error appears stating "subTree" error.​
Project Visibility: Despite the error, the child projects remain visible in the Projects tab.​ (figure 1, 2)
Accessing Child Projects: When attempting to access a child project, a notification indicates that the project is archived.​ (figure 3)
Disappearance from Tab: Subsequently, the child project disappears from the Projects tab.​ (figure 4)

While this behavior is not critical, it appears to be an unintended consequence of the archiving process. I would appreciate any insights or suggestions on how to address this issue.​

Vikunja Version

0.24.6

Browser and version

Chrome 135.0.7049.85

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

Image
Image
Image
Image

Originally created by @key262yek on GitHub (Apr 23, 2025). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/691 ### Description I have encountered an issue when archiving a parent project that contains child projects which have not been archived. Upon attempting this, I observed the following sequence: Error Message: An error appears stating "subTree" error.​ Project Visibility: Despite the error, the child projects remain visible in the Projects tab.​ (figure 1, 2) Accessing Child Projects: When attempting to access a child project, a notification indicates that the project is archived.​ (figure 3) Disappearance from Tab: Subsequently, the child project disappears from the Projects tab.​ (figure 4) While this behavior is not critical, it appears to be an unintended consequence of the archiving process. I would appreciate any insights or suggestions on how to address this issue.​ ### Vikunja Version 0.24.6 ### Browser and version Chrome 135.0.7049.85 ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots ![Image](https://github.com/user-attachments/assets/32bae063-e4ca-404e-8154-bbd8982f6345) ![Image](https://github.com/user-attachments/assets/4154b2da-b0bf-4afb-ad31-9c66908ba0bf) ![Image](https://github.com/user-attachments/assets/fc18d935-b4d3-4002-96eb-f029282ab4cc) ![Image](https://github.com/user-attachments/assets/f9d89b2a-9e38-4d44-821b-9b781e29fbe5)
GiteaMirror commented 2026-04-20 16:52:09 -05:00
Author
Owner
Copy Link

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

Will be resolved by https://github.com/go-vikunja/vikunja/pull/775

<!-- gh-comment-id:2883856449 --> @kolaente commented on GitHub (May 15, 2025): Will be resolved by https://github.com/go-vikunja/vikunja/pull/775
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#6288
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?