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

Add Attachment with less clicks #582

New Issue
Open
opened 2025-11-01 20:59:42 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-01 20:59:42 -05:00
Owner
Copy Link

Originally created by @xeruf on GitHub (Sep 2, 2025).

Description

When I click add attachments in the sidebar, I have to click again to add an attachment in the menu that shows up - I think that second click should not be necessary, when I add attachments in the sidebar, it should automatically show the system dialogue.

Which alternatives did you consider using instead?

No response

Originally created by @xeruf on GitHub (Sep 2, 2025). ### Description When I click add attachments in the sidebar, I have to click again to add an attachment in the menu that shows up - I think that second click should not be necessary, when I add attachments in the sidebar, it should automatically show the system dialogue. ### Which alternatives did you consider using instead? _No response_
GiteaMirror commented 2025-11-01 20:59:43 -05:00
Author
Owner
Copy Link

@Saturo78 commented on GitHub (Sep 2, 2025):

I like that kind of logic.
First click activates field, second click set value or upload attachment.
the due date field works the same way.

@Saturo78 commented on GitHub (Sep 2, 2025): I like that kind of logic. First click activates field, second click set value or upload attachment. the due date field works the same way.
GiteaMirror commented 2025-11-01 20:59:43 -05:00
Author
Owner
Copy Link

@xeruf commented on GitHub (Sep 3, 2025):

but what's the point of the extra click? I only click the sidebar button if I want to add an attachment, so why click again?

@xeruf commented on GitHub (Sep 3, 2025): but what's the point of the extra click? I only click the sidebar button if I want to add an attachment, so why click again?
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#582
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?