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

[Enhancement] KanBan: Save Order Of Issues on Boards #11161

Closed
6543 opened this issue Apr 20, 2020 · 4 comments · Fixed by #17152
Closed

[Enhancement] KanBan: Save Order Of Issues on Boards #11161

6543 opened this issue Apr 20, 2020 · 4 comments · Fixed by #17152
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented topic/projects type/enhancement An improvement of existing functionality

Comments

@6543
Copy link
Member

6543 commented Apr 20, 2020

Add a filed ProjectBoardOrder or use Priority from/to Issue struct.
0 = default
highest number is on the top of the list ...

thoughts how to impement the backend:

issue with prio 4 -> 2:
new prio is lower so "Update prio=prio+1 where issue.project_id= .... and prio >= 2 and prio < 4"
issue with prio 3 -> 7:
else "Update prio=prio-1 where issue.project_id= .... and prio > 3 and prio <= 7"
x.ID(issue.id).UpdateCol(prio=newPrio)

Pseudo code don't take it to serious

Blocked by #8346

@6543 6543 mentioned this issue Apr 20, 2020
13 tasks
@stale
Copy link

stale bot commented Jun 20, 2020

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale stale bot added the issue/stale label Jun 20, 2020
@6543
Copy link
Member Author

6543 commented Jun 20, 2020

kanban was not merged jet

@stale stale bot removed the issue/stale label Jun 20, 2020
@lunny lunny added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Jun 21, 2020
@6543 6543 mentioned this issue Aug 17, 2020
3 tasks
@6543
Copy link
Member Author

6543 commented Aug 17, 2020

will be closed by #12506

@JosephLucas
Copy link

Unfortunately PR #12506 has been closed by @patcito that "cannot commit to redo the backend" (needed to fulfill reviewer requests). Is there any plan for a sustainable order of issues in the kanban ?

@lunny lunny mentioned this issue Feb 17, 2021
15 tasks
@axifive axifive added the type/enhancement An improvement of existing functionality label Sep 25, 2021
@go-gitea go-gitea locked and limited conversation to collaborators Apr 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented topic/projects type/enhancement An improvement of existing functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants