Allow hiding of closed issues in project board #467

Open
opened 2 weeks ago by fnetX · 1 comments
fnetX commented 2 weeks ago
Collaborator
Transfer from Mastodon: https://fosstodon.org/@tychosoft/106380662669506991

In my normal workflow, I prefer to have items disappear from visibility in project boards when they are completed (closed, merged, etc). My suggestion is adding a slider on #gitea project boards to show/hide completed items.

that's why I suggest it as a toggle for the repo owner to set for each project (or globally per repo settings). Some really don't want to see closed issues crowding a board, and some do want to see what has been accomplished. I think of it as a board level setting (by the project owner) rather than tracking per each user profile per board which seems a massive database overreach ;). I can add something of a suggestion issue in the bug tracker.

###### Transfer from Mastodon: https://fosstodon.org/@tychosoft/106380662669506991 --- In my normal workflow, I prefer to have items disappear from visibility in project boards when they are completed (closed, merged, etc). My suggestion is adding a slider on #gitea project boards to show/hide completed items. that's why I suggest it as a toggle for the repo owner to set for each project (or globally per repo settings). Some really don't want to see closed issues crowding a board, and some do want to see what has been accomplished. I think of it as a board level setting (by the project owner) rather than tracking per each user profile per board which seems a massive database overreach ;). I can add something of a suggestion issue in the bug tracker.
fnetX added the
enhancement
contribution welcome
gitea-related
labels 2 weeks ago

I could comment on this and elaborate a bit, as I was going to post it here :).

One reason I see this as desirable is that one might be tracking issues on an issue board, and using the Closes # capability in the pull request, which automatically closes an associated issue when the PR is merged. This could of course close an issue regardless of where it is on the board, but still leaves it on the board.

Many may want to move closed issues (or merged PR's) to a "closed" column on the right, just as they begin in a default column on the left. But this is a manual operation currently, rather than automatic. At least some may simply not want to see closed issues in a project board at all, but again this involves manually clearing the project in the issue. This suggestion really is to impliment a means of automating these common workflow issues with project boards, and the particular way I was suggesting to do so is just one kind of possibility.

For example, an alternate way to accomplish this, rather than a show/hide toggle, might be to be able to choose a default board in the project to "close to", much like the "default" board for new issues. If it's chosen it also becomes the right side board, just as the "default" becomes the left side board, and if there is no chosen "close to" board, then closed issues or pr's are not shown. I suspect a show/hide toggle is probably the simplest to impliment with the fewest changes, though.

Incidentally gitlab uses fixed "closed" and "default" board columns that cannot be altered at all in their project board views, and closed things automatically do move to the closed column. However, the default and closed columns can each be "collapsed", which means they become real skinny and don't show much, which is almost the same as being hidden. I think gitea's handling of having uncategorized board by default and picking a default column is more consistent rather than having special fixed columns with different ui appearences possible, especially if closed items can be optionally entirely hidden in some manner.

I could comment on this and elaborate a bit, as I was going to post it here :). One reason I see this as desirable is that one might be tracking issues on an issue board, and using the Closes # capability in the pull request, which automatically closes an associated issue when the PR is merged. This could of course close an issue regardless of where it is on the board, but still leaves it on the board. Many may want to move closed issues (or merged PR's) to a "closed" column on the right, just as they begin in a default column on the left. But this is a manual operation currently, rather than automatic. At least some may simply not want to see closed issues in a project board at all, but again this involves manually clearing the project in the issue. This suggestion really is to impliment a means of automating these common workflow issues with project boards, and the particular way I was suggesting to do so is just one kind of possibility. For example, an alternate way to accomplish this, rather than a show/hide toggle, might be to be able to choose a default board in the project to "close to", much like the "default" board for new issues. If it's chosen it also becomes the right side board, just as the "default" becomes the left side board, and if there is no chosen "close to" board, then closed issues or pr's are not shown. I suspect a show/hide toggle is probably the simplest to impliment with the fewest changes, though. Incidentally gitlab uses fixed "closed" and "default" board columns that cannot be altered at all in their project board views, and closed things automatically do move to the closed column. However, the default and closed columns can each be "collapsed", which means they become real skinny and don't show much, which is almost the same as being hidden. I think gitea's handling of having uncategorized board by default and picking a default column is more consistent rather than having special fixed columns with different ui appearences possible, especially if closed items can be optionally entirely hidden in some manner.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.