starred/vikunja-go-vikunja

Fork 0

mirror of https://github.com/go-vikunja/vikunja.git synced 2026-03-03 00:46:57 -05:00

Expand the area into which kanban items can be dragged to change column #31

New issue

Closed

opened 2026-02-27 14:50:08 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-27 14:50:08 -05:00

Owner

Originally created by @jacquesh on GitHub (Feb 8, 2022).

Here is an example of a simple kanban board in vikunja:

The green arrows show where I can drag the selected item ("item 4") to move it to one of the other columns. The red arrows show places where I would like to be able to drag the item but that I can't (it doesn't recognise that this is part of the other column).

It'd be helpful if the columns extended all the way to the bottom of the screen (conceptually, for the purposes of drag-and-drop) because that would make it much easier & faster to drag items between columns. Currently you have to drag the item to a fairly small & specific position to get it to detect that this item should go to another column.

Originally created by @jacquesh on GitHub (Feb 8, 2022). Here is an example of a simple kanban board in vikunja: ![image](https://user-images.githubusercontent.com/4639662/153038935-e164f624-2c0d-475b-bc7b-a40c1e00dbbd.png) The green arrows show where I can drag the selected item ("item 4") to move it to one of the other columns. The red arrows show places where I would *like* to be able to drag the item but that I can't (it doesn't recognise that this is part of the other column). It'd be helpful if the columns extended all the way to the bottom of the screen (conceptually, for the purposes of drag-and-drop) because that would make it much easier & faster to drag items between columns. Currently you have to drag the item to a fairly small & specific position to get it to detect that this item should go to another column.

deekerman

2026-02-27 14:50:08 -05:00

closed this issue
added the
enhancement
label

deekerman commented

2026-02-27 14:50:13 -05:00

Author

Owner

@dpschen commented on GitHub (Feb 8, 2022):

This will be fixed by https://kolaente.dev/vikunja/frontend/pulls/1512

@dpschen commented on GitHub (Feb 8, 2022): This will be fixed by https://kolaente.dev/vikunja/frontend/pulls/1512

deekerman commented

2026-02-27 14:50:13 -05:00

Author

Owner

@kolaente commented on GitHub (Feb 13, 2022):

Fixed in https://kolaente.dev/vikunja/frontend/pulls/1512 - will be included in the next unstable release. Please check with that once the CI released it (in ~30 min).

@kolaente commented on GitHub (Feb 13, 2022): Fixed in https://kolaente.dev/vikunja/frontend/pulls/1512 - will be included in the next unstable release. Please check with that once the CI released it (in ~30 min).

deekerman commented

2026-02-27 14:50:13 -05:00

Author

Owner

@jacquesh commented on GitHub (Feb 14, 2022):

Awesome, yeah that feels much better (I think). Thanks for the quick turnaround from the both of you! <3

@jacquesh commented on GitHub (Feb 14, 2022): Awesome, yeah that feels much better (I think). Thanks for the quick turnaround from the both of you! <3

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/vikunja-go-vikunja#31

No description provided.

Rows
Columns