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

Improve sharing with team #2144

New Issue
Closed
opened 2026-03-22 13:56:21 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-03-22 13:56:21 -05:00
Owner
Copy Link

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

Original issue by dpschen on 2022-09-14T08:48:15.000Z

Version information:

Frontend Version: dev
API Version: dev
Browser and OS Version: all

Steps to reproduce:

  1. Don't be in any team
  2. Open the team share modal

Expected behavior:

The 'Shared with these teams' area is not shown

Actual behavior:

The 'Shared with these teams' is shown. See screenshot:

image

Checklist:

  • I have provided all required information
  • I am using the latest release or the latest unstable build
  • I was able to reproduce the bug on try

Original issue on Gitea

@kolaente commented on 2022-09-14T12:43:49.000Z:

So the "Shared with these teams" area should not be shown if the user is not in any team?

I wouldn't consider this a bug but a UX-improvement.

dpschen commented on 2022-09-14T13:51:13.000Z:

I see it as a bug, since the user is shown some control elements that don't have functionality for him, aka are broken.

I thought that removing the controls completely would be the best choice if the user isn't part of any team because it seems to indicate that the installation is for a single-user only, thus no teams necessary. Showing the UI in this case might be confusing or distracting / congesting the ui.

In case I oversaw something and there could be other reasons why there is no team available we could disable the UI instead and inform that the user needs to be in a team in order to share it with one.

Originally created by @vikunja-bot on GitHub (Apr 1, 2025). _Original issue by dpschen on 2022-09-14T08:48:15.000Z_ <!-- Please fill out this issue template to report a bug. If you want to propose a new feature, please open a discussion thread in the forum: https://community.vikunja.io --> **Version information:** Frontend Version: dev API Version: dev Browser and OS Version: all **Steps to reproduce:** <!-- Add clear steps to reproduce the bug. Provide screenshots where applicable. --> 1. Don't be in any team 2. Open the team share modal **Expected behavior:** <!-- Describe what happened. --> The 'Shared with these teams' area is not shown **Actual behavior:** <!-- Describe what happened instead. --> The 'Shared with these teams' is shown. See screenshot: ![image](/attachments/656070fe-1cc9-4a68-a8c6-773c2af924f7) **Checklist:** * [x] I have provided all required information * [x] I am using the latest release or the latest unstable build * [x] I was able to reproduce the bug on [try](https://try.vikunja.io) [Original issue on Gitea](https://kolaente.dev/vikunja/vikunja/issues/1979) --- _**@kolaente** commented on 2022-09-14T12:43:49.000Z_: So the "Shared with these teams" area should not be shown if the user is not in any team? I wouldn't consider this a bug but a UX-improvement. --- _**dpschen** commented on 2022-09-14T13:51:13.000Z_: I see it as a bug, since the user is shown some control elements that don't have functionality for him, aka are broken. I thought that removing the controls completely would be the best choice if the user isn't part of any team because it seems to indicate that the installation is for a single-user only, thus no teams necessary. Showing the UI in this case might be confusing or distracting / congesting the ui. In case I oversaw something and there could be other reasons why there is no team available we could disable the UI instead and inform that the user needs to be in a team in order to share it with one.
GiteaMirror commented 2026-03-22 13:56:21 -05:00
Author
Owner
Copy Link

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

@dpschen is this still a problem?

@kolaente commented on GitHub (Jun 24, 2025): @dpschen is this still a problem?
GiteaMirror commented 2026-03-22 13:56:22 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Aug 3, 2025):

Closing as kind of resolved - please ping if this is still a problem.

@kolaente commented on GitHub (Aug 3, 2025): Closing as kind of resolved - please ping if this is still a problem.
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#2144
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?