Dragging items between and within columns in project boards #14087

New Issue

GiteaMirror · 2025-11-02T11:02:29-06:00

GiteaMirror commented

2025-11-02 11:02:29 -06:00

Originally created by @bartvdbraak on GitHub (Feb 3, 2025).

Description

Our triagers reported the following user experience issues with Project boards after updating to Gitea 1.23.1:

Project boards are now displayed as a table where the height matches the tallest column. Previously, they were constrained to fit within the browser view, with individual scrollbars for each column. This change makes dragging items between columns—especially from the bottom of one column to the top of another—more difficult.
(resolved) ~~Moving an item laterally within a project board column appears to trigger an event, when it should likely just update its column placement.~~

(screenshot for 2, resolved)

Gitea Version

1.23.1 built with GNU Make 4.4.1, go1.23.5 : bindata, timetzdata, sqlite, sqlite_unlock_notify

Originally created by @bartvdbraak on GitHub (Feb 3, 2025). ### Description Our triagers reported the following user experience issues with Project boards after updating to Gitea 1.23.1: - Project boards are now displayed as a table where the height matches the tallest column. Previously, they were constrained to fit within the browser view, with individual scrollbars for each column. This change makes dragging items between columns—especially from the bottom of one column to the top of another—more difficult. - (resolved) ~~Moving an item laterally within a project board column appears to trigger an event, when it should likely just update its column placement.~~ <details> <summary> (screenshot for 2, resolved)</summary> ![Image](https://github.com/user-attachments/assets/6e09c4cf-f813-4711-bb28-9336f4805b78) <details> ### Gitea Version 1.23.1 built with GNU Make 4.4.1, go1.23.5 : bindata, timetzdata, sqlite, sqlite_unlock_notify

GiteaMirror added the type/bug label 2025-11-02 11:02:29 -06:00

GiteaMirror closed this issue

2025-11-02 11:02:29 -06:00

GiteaMirror commented

2025-11-02 11:02:30 -06:00

@wxiaoguang commented on GitHub (Feb 3, 2025):

Workboards are now displayed as a table where the height matches the tallest column. Previously, they were constrained to fit within the browser view, with individual scrollbars for each column. This change makes dragging items between columns—especially from the bottom of one column to the top of another—more difficult.

Related to feat(#31666): Set the columns height to hug all its contents (#31726) ?

(Just FYI, I haven't really looked into it, help is welcome!)

the second one (moving issue in column) has been resolved

Moving an item laterally within a Workboard column appears to trigger an event, when it should likely just update its column placement.

~~Related to Add issue comment when moving issues from one column to another of the project (#29311)~~ FIXED BY #33496 and its backport

@wxiaoguang commented on GitHub (Feb 3, 2025): > * Workboards are now displayed as a table where the height matches the tallest column. Previously, they were constrained to fit within the browser view, with individual scrollbars for each column. This change makes dragging items between columns—especially from the bottom of one column to the top of another—more difficult. Related to feat(#31666): Set the columns height to hug all its contents (#31726) ? * (Just FYI, I haven't really looked into it, help is welcome!) <details> <summary> the second one (moving issue in column) has been resolved</summary> > * Moving an item laterally within a Workboard column appears to trigger an event, when it should likely just update its column placement. ~~Related to Add issue comment when moving issues from one column to another of the project (#29311)~~ FIXED BY #33496 and its backport </deatils>

GiteaMirror commented

2025-11-02 11:02:30 -06:00

@lunny commented on GitHub (Feb 3, 2025):

Workboards are now displayed as a table where the height matches the tallest column. Previously, they were constrained to fit within the browser view, with individual scrollbars for each column. This change makes dragging items between columns—especially from the bottom of one column to the top of another—more difficult.

Related to feat(#31666): Set the columns height to hug all its contents (#31726) ?

Moving an item laterally within a Workboard column appears to trigger an event, when it should likely just update its column placement.

Related to Add issue comment when moving issues from one column to another of the project (#29311) @lunny

#29311 is a follow-up design to what GitHub did.

@lunny commented on GitHub (Feb 3, 2025): > > * Workboards are now displayed as a table where the height matches the tallest column. Previously, they were constrained to fit within the browser view, with individual scrollbars for each column. This change makes dragging items between columns—especially from the bottom of one column to the top of another—more difficult. > > Related to feat([#31666](https://github.com/go-gitea/gitea/issues/31666)): Set the columns height to hug all its contents ([#31726](https://github.com/go-gitea/gitea/pull/31726)) ? > > > * Moving an item laterally within a Workboard column appears to trigger an event, when it should likely just update its column placement. > > Related to Add issue comment when moving issues from one column to another of the project ([#29311](https://github.com/go-gitea/gitea/pull/29311)) [<img alt="" width="16" height="16" src="https://avatars.githubusercontent.com/u/81045?s=64&u=99b64f0ca6ef63643c7583ab87dd31c52d28e673&v=4">@lunny](https://github.com/lunny) #29311 is a follow-up design to what GitHub did.

GiteaMirror commented

2025-11-02 11:02:30 -06:00

@wxiaoguang commented on GitHub (Feb 4, 2025):

Moving an item laterally within a Workboard column appears to trigger an event, when it should likely just update its column placement.

Related to Add issue comment when moving issues from one column to another of the project (#29311) @lunny

#29311 is a follow-up design to what GitHub did.

Are you sure that GitHub also creates such useless noise when moving the issue in the same column?

@wxiaoguang commented on GitHub (Feb 4, 2025): > > > * Moving an item laterally within a Workboard column appears to trigger an event, when it should likely just update its column placement. > > > > > > Related to Add issue comment when moving issues from one column to another of the project ([#29311](https://github.com/go-gitea/gitea/pull/29311)) [<img alt="" width="16" height="16" src="https://avatars.githubusercontent.com/u/81045?s=64&u=99b64f0ca6ef63643c7583ab87dd31c52d28e673&v=4">@lunny](https://github.com/lunny) > > [#29311](https://github.com/go-gitea/gitea/pull/29311) is a follow-up design to what GitHub did. Are you sure that GitHub also creates such useless noise when moving the issue in the same column?

GiteaMirror commented

2025-11-02 11:02:30 -06:00

@lunny commented on GitHub (Feb 4, 2025):

Moving an item laterally within a Workboard column appears to trigger an event, when it should likely just update its column placement.

Related to Add issue comment when moving issues from one column to another of the project (#29311) @lunny

#29311 is a follow-up design to what GitHub did.

Are you sure that GitHub also creates such useless noise when moving the issue in the same column?

I think I'm wrong. Moving in the same column with different positons should not trigger a comment. #33496

@lunny commented on GitHub (Feb 4, 2025): > > > > * Moving an item laterally within a Workboard column appears to trigger an event, when it should likely just update its column placement. > > > > > > > > > Related to Add issue comment when moving issues from one column to another of the project ([#29311](https://github.com/go-gitea/gitea/pull/29311)) [<img alt="" width="16" height="16" src="https://avatars.githubusercontent.com/u/81045?s=64&u=99b64f0ca6ef63643c7583ab87dd31c52d28e673&v=4">@lunny](https://github.com/lunny) > > > > > > [#29311](https://github.com/go-gitea/gitea/pull/29311) is a follow-up design to what GitHub did. > > Are you sure that GitHub also creates such useless noise when moving the issue in the same column? I think I'm wrong. Moving in the same column with different positons should not trigger a comment. #33496

GiteaMirror commented

2025-11-02 11:02:31 -06:00

@wxiaoguang commented on GitHub (Feb 5, 2025):

The first one is still unresolved (ps: actually I haven't really looked into it, if anyone has ideas, welcome to help, thank you!)

@wxiaoguang commented on GitHub (Feb 5, 2025): The first one is still unresolved (ps: actually I haven't really looked into it, if anyone has ideas, welcome to help, thank you!)

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#14087