When deleting a card in kanban, it remains in its list until page refresh #105

Closed
opened 2025-11-01 20:47:10 -05:00 by GiteaMirror · 2 comments
Owner

Originally created by @canadaduane on GitHub (Nov 12, 2022).

Description

  1. a kanban card is in the "Done" list (for example)
  2. click on the card to show all of its details & action buttons
  3. click red "delete" action button at the bottom
  4. the view goes back to the kanban columns, but the card is still there
  5. if I click on the card, Vikunja shows a "404" error "The list task does not exist"

I expect the kanban card to be deleted and no longer visible in the column/list it was shown in before.

Vikunja Frontend Version

0.20.0

Vikunja API Version

0.20.0

Browser and version

Firefox 106.0.1

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

No response

Originally created by @canadaduane on GitHub (Nov 12, 2022). ### Description 1. a kanban card is in the "Done" list (for example) 2. click on the card to show all of its details & action buttons 3. click red "delete" action button at the bottom 4. the view goes back to the kanban columns, but the card is still there 5. if I click on the card, Vikunja shows a "404" error "The list task does not exist" I expect the kanban card to be deleted and no longer visible in the column/list it was shown in before. ### Vikunja Frontend Version 0.20.0 ### Vikunja API Version 0.20.0 ### Browser and version Firefox 106.0.1 ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots _No response_
GiteaMirror added the bug label 2025-11-01 20:47:10 -05:00
Author
Owner

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

Looks like this only happens when deleting a task which is in the first bucket.

@kolaente commented on GitHub (Nov 12, 2022): Looks like this only happens when deleting a task which is in the first bucket.
Author
Owner

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

Should be fixed in 995cc12880. Please check with the next unstable build (~30 min) if the problem really went away.

@kolaente commented on GitHub (Nov 12, 2022): Should be fixed in https://github.com/go-vikunja/frontend/commit/995cc12880e3e23a018fb1f86f601b287f5955df. Please check with the next unstable build (~30 min) if the problem really went away.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#105