Sub Project improvement views #3794
Labels
No Label
area/internal-code
changes requested
confirmed
dependencies
duplicate
good first issue
help wanted
hosting
invalid
kind/bug
kind/feature
question
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/frontend#3794
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Description
Hello :)
there are some features that could be added to improve project view and be useful:
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
Sub Project improvement viewsto Sub Project improvement viewsThe 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.
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.