Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] KanBan: allow to change the order of "boards" and other properties of "boards" #14709

Closed
datenheim opened this issue Feb 17, 2021 · 3 comments

Comments

@datenheim
Copy link

  • Gitea version (or commit ref): 1.13.0

Description

Give some sort of control over the order of so called "boards" (or panes).

Right now their order is bit out of control, and after renamed a board, the order has changed.
Could be drag and drop (#13805), or a numeric option or whatever.

If a numeric option, it could be placed in the dialogue currently allowing to rename the board.

Of course any board shoulb be renamable, also the default one, #14679

Also one might add an option to color the board, relates to #11160

And an option to input a description of the board, relates to #12513

@datenheim datenheim changed the title [Feature Request] KanBan: allow to change the order of "boards" and other properties [Feature Request] KanBan: allow to change the order of "boards" and other properties of "boards" Feb 17, 2021
@lunny lunny mentioned this issue Feb 17, 2021
15 tasks
@delvh
Copy link
Member

delvh commented Feb 17, 2021

Give some sort of control over the order of so called "boards" (or panes).
Right now their order is bit out of control, and after renamed a board, the order has changed.
Could be drag and drop (#13805), or a numeric option or whatever.
If a numeric option, it could be placed in the dialogue currently allowing to rename the board.

Should already be a part of 1.14 (see #14533 and its merged PR #14634).

I agree however that the other mentioned points (board color, board renaming and board notes) are valid feature requests. Maybe delete the first paragraphs and rename the issue.

@lunny
Copy link
Member

lunny commented Feb 18, 2021

Duplicated with #13805.

@lunny lunny closed this as completed Feb 18, 2021
@datenheim
Copy link
Author

@lunny thanks for taking the points to the summary

@go-gitea go-gitea locked and limited conversation to collaborators May 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants