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

Labels will be created multiple times when using the multi line add function #110

New Issue
Closed
opened 2025-11-01 20:47:21 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-01 20:47:21 -05:00
Owner
Copy Link

Originally created by @chrisb86 on GitHub (Nov 18, 2022).

Description

When adding multiple tasks at once while adding labes with the quick add magic, all labels will be created multiple times, even if they are named the same.

eg.

Task 1 *label-foo
Task 2 *label-bla
Task 3 *label-foo

Leads to creation of the labels label-foo, label-foo and label-bla.

Vikunja Frontend Version

0.20.1

Vikunja API Version

0.20.1

Browser and version

Firefox 107.0

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

Bildschirm­foto 2022-11-19 um 00 55 01 Bildschirm­foto 2022-11-19 um 00 54 35
Originally created by @chrisb86 on GitHub (Nov 18, 2022). ### Description When adding multiple tasks at once while adding labes with the quick add magic, all labels will be created multiple times, even if they are named the same. eg. Task 1 *label-foo Task 2 *label-bla Task 3 *label-foo Leads to creation of the labels label-foo, label-foo and label-bla. ### Vikunja Frontend Version 0.20.1 ### Vikunja API Version 0.20.1 ### Browser and version Firefox 107.0 ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots <img width="1474" alt="Bildschirm­foto 2022-11-19 um 00 55 01" src="https://user-images.githubusercontent.com/560571/202822062-fb549f4d-4317-4211-acb1-497c5000cabd.png"> <img width="1474" alt="Bildschirm­foto 2022-11-19 um 00 54 35" src="https://user-images.githubusercontent.com/560571/202822058-2331f9a6-5d67-4d3f-b470-186d01195f06.png">
GiteaMirror added the bug label 2025-11-01 20:47:21 -05:00
GiteaMirror commented 2025-11-01 20:47:24 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 21, 2022):

Looks like this is only the case when creating multiple tasks at once with a label that did not exist previously. Existing labels are correctly used multiple times.

@kolaente commented on GitHub (Nov 21, 2022): Looks like this is only the case when creating multiple tasks at once with a label that did not exist previously. Existing labels are correctly used multiple times.
GiteaMirror commented 2025-11-01 20:47:24 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Dec 4, 2022):

Fixed in 463d22b07c. Please check with the next unstable release (~30 min or on try) if the problem really went away.

@kolaente commented on GitHub (Dec 4, 2022): Fixed in 463d22b07ca75c91a6453c59ebdc3cb56ee61f96. Please check with the next unstable release (~30 min or on try) if the problem really went away.
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 bug
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#110
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?