<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=24346) </details> <!--IssueSummary end--> ### Problem to solve Currently issue boards do have a way to prioritize issues on order as described in gitlab-ce#21264. But this system should get some improvements to allow a better scrum/agile work method. ### Further details We are using a issue board as a scrum board for the current sprint. Which means we need all issues in the `OPEN` column ordered with the most added value on top and least added value at the bottom. After the `OPEN` column we have columns like `doing`, `waiting for approval`, `approval in progress`, etc. and at last we have the `CLOSED`. Some issues with ordering in these boards arise or could be improved, being: 1. We can only change the ordering in the `OPEN` column by moving issues from the bottom to the top. When we try to put an issue from the top to the bottom it won't save this order. This seems like a gitlab-ce~2278648 to me for issue gitlab-ce#21264. 2. When issues are moved from `OPEN` to the 2nd lane and from the 2nd lane to the third lane it would be nice to keep the order in place. Meaning the one with the top priority in `OPEN` will be the top one in 2nd lane etc. 3. Even if issues are in the `CLOSED` and are reopened during the sprint. It should be priority number 1 in the `OPEN` 4. It also looks like everyone (maintainers, developers, reporters) can all re-order the priority in the boards. I think this should be a maintainer feature at least.