github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-07-26 22:50:27 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

Sub Project improvement views #458

New Issue
Open
opened 2025-11-01 20:56:28 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-01 20:56:28 -05:00
Owner
Copy Link
Copy Source

Originally created by @vikunja-bot on GitHub (Apr 1, 2025).

Original issue by massimiliano-dalcero on 2023-10-23T07:54:42.000Z

Description

Hello :)

there are some features that could be added to improve project view and be useful:

  • List of sub-projects (an example in screenshot, but there may be better graphical solutions)
  • Ability to view tasks from sub-projects from parents (with the option to choose the level)
  • Display the parents of the current project (like breadcrumbs)

I think they are aesthetic suggestions capable of improving usability and effectiveness.

Note:
the screenshots are just to explain, not to suggest how to implement them :)

Best Regards,
Massimiliano

Vikunja Frontend Version

0.21.0+297-2eac17ed57

Vikunja API Version

v0.21.0+178-aad6bc08f6

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

image

image

Original issue on Gitea

@kolaente commented on 2023-10-27T15:30:22.000Z:

The problem with breadcrumbs is they can get too large to show them in the title bar. On the task detail view, you should already see the breadcrumbs.

What does not work for you with the list of sub projects in the sidebar?

Also this is not a bug, please use the forum for feature discussions in the future.

massimiliano-dalcero commented on 2023-10-28T08:37:45.000Z:

Hello 😊

When you're in the sub-project view, you might not have a clear awareness of where THAT sub-project is. Different distinct but similar main projects (e.g., different customers) could have sub-projects with the same name because they serve the same purposes.

So, when you're in a sub-project, it's not immediately obvious which main project you're in.

Of course, you could use a naming convention for sub-projects (eg: $CUSTOMER - $MAINPROJECT - $SUBPROJECT"), but in my opinion, it would bit of a forced.

dpschen commented on 2024-07-17T21:15:03.000Z:

Unsure, but maybe we should highlight the parent project in the sidebar if the current subproject is inside. This makes a lot of sense if the parent project is collapsed.

Possible alternative / combination:

Automatically expand parent projects if navigating to a project.

Implementation idea in NavigationItem
For this I wouldn't change the open state but instead add some new state, something like forcedShown. When navigating to some subproject we would initially check if the NavigationItem includes the current project and set forcedShown accordingly.

The parent would be displayed open if open OR forcedShown is true.

If the user then tries to close the parent project manually, we would first check the open state, and if that is already false we would try to set a forcedShown to false.

When leaving a project the forcedShown should be reset.

dpschen commented on 2024-07-17T21:17:43.000Z:

Regarding the breadcrumbs:

We could build one breadcrumb component that contains this functionality and use it in the task details as well as on the project pages.

It would display info depending on available space. Mobile there would also be the possibility of a sidescroller. I would avoid that on desktop and hide overflowing items in a dropdown menu.

Originally created by @vikunja-bot on GitHub (Apr 1, 2025). _Original issue by massimiliano-dalcero on 2023-10-23T07:54:42.000Z_ ### Description Hello :) there are some features that could be added to improve project view and be useful: - List of sub-projects (an example in screenshot, but there may be better graphical solutions) - Ability to view tasks from sub-projects from parents (with the option to choose the level) - Display the parents of the current project (like breadcrumbs) I think they are aesthetic suggestions capable of improving usability and effectiveness. Note: the screenshots are just to explain, not to suggest how to implement them :) Best Regards, Massimiliano ### Vikunja Frontend Version 0.21.0+297-2eac17ed57 ### Vikunja API Version v0.21.0+178-aad6bc08f6 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots ![image](/attachments/61c6e285-160a-401e-8b8c-12cb70837d6f) ![image](/attachments/82202994-22d8-4f2f-9aca-2fdcb19dcb7e) [Original issue on Gitea](https://kolaente.dev/vikunja/vikunja/issues/2076) --- _**@kolaente** commented on 2023-10-27T15:30:22.000Z_: The problem with breadcrumbs is they can get too large to show them in the title bar. On the task detail view, you should already see the breadcrumbs. What does not work for you with the list of sub projects in the sidebar? Also this is not a bug, please use the forum for feature discussions in the future. --- _**massimiliano-dalcero** commented on 2023-10-28T08:37:45.000Z_: Hello 😊 When you're in the sub-project view, you might not have a clear awareness of where THAT sub-project is. Different distinct but similar main projects (e.g., different customers) could have sub-projects with the same name because they serve the same purposes. So, when you're in a sub-project, it's not immediately obvious which main project you're in. Of course, you could use a naming convention for sub-projects (eg: $CUSTOMER - $MAINPROJECT - $SUBPROJECT"), but in my opinion, it would bit of a forced. --- _**dpschen** commented on 2024-07-17T21:15:03.000Z_: Unsure, but maybe we should highlight the parent project in the sidebar if the current subproject is inside. This makes a lot of sense if the parent project is collapsed. Possible alternative / combination: Automatically expand parent projects if navigating to a project. ----- *Implementation idea in `NavigationItem`* For this I wouldn't change the `open` state but instead add some new state, something like `forcedShown`. When navigating to some subproject we would initially check if the NavigationItem includes the current project and set `forcedShown` accordingly. The parent would be displayed open if `open` OR `forcedShown` is `true`. If the user then tries to close the parent project manually, we would first check the `open` state, and if that is already `false` we would try to set a `forcedShown` to false. When leaving a project the forcedShown should be reset. ----- --- _**dpschen** commented on 2024-07-17T21:17:43.000Z_: Regarding the breadcrumbs: We could build one breadcrumb component that contains this functionality and use it in the task details as well as on the project pages. It would display info depending on available space. Mobile there would also be the possibility of a sidescroller. I would avoid that on desktop and hide overflowing items in a dropdown menu.
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 labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#458