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

New Issue

GiteaMirror · 2025-11-02T06:20:03-06:00

GiteaMirror commented

2025-11-02 06:20:03 -06:00

Originally created by @6543 on GitHub (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

Originally created by @6543 on GitHub (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

GiteaMirror added the topic/projects issue/confirmed type/enhancement labels 2025-11-02 06:20:03 -06:00

GiteaMirror closed this issue

2025-11-02 06:20:03 -06:00

GiteaMirror commented

2025-11-02 06:20:04 -06:00

@stale[bot] commented on GitHub (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[bot] commented on GitHub (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.

GiteaMirror commented

2025-11-02 06:20:04 -06:00

@6543 commented on GitHub (Jun 20, 2020):

kanban was not merged jet

@6543 commented on GitHub (Jun 20, 2020): kanban was not merged jet

GiteaMirror commented

2025-11-02 06:20:04 -06:00

@6543 commented on GitHub (Aug 17, 2020):

will be closed by #12506

@6543 commented on GitHub (Aug 17, 2020): will be closed by #12506

GiteaMirror commented

2025-11-02 06:20:04 -06:00

@JosephLucas commented on GitHub (Jan 6, 2021):

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 ?

@JosephLucas commented on GitHub (Jan 6, 2021): 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 ?

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#5277