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

[bug]: priority sorting is broken #2916

Closed
1 task done
pmig opened this issue Nov 28, 2023 · 3 comments · Fixed by #3141
Closed
1 task done

[bug]: priority sorting is broken #2916

pmig opened this issue Nov 28, 2023 · 3 comments · Fixed by #3141
Assignees
Labels
🐛bug Something isn't working

Comments

@pmig
Copy link

pmig commented Nov 28, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Current behavior

When organizing tickets in cycles and working in the Kanban view tickets are sorted by priority. (but alphabetically and not actual priority)

sort oder:

high
low
medium
none
urgent

Correct behavior:

urgent
high
medium
low
none

Steps to reproduce

Open Kanban view and give tickets priorities

Browser

Google Chrome

Version

Self-hosted

@vihar
Copy link
Contributor

vihar commented Nov 29, 2023

@pmig, we are currently redesigning the layout of our entire Kanban board for improved performance. This issue has already been addressed and resolved on #2941. The fix will be included in the upcoming 0.14-dev release. We will update you as soon as the release is available.

@kotasudhakar
Copy link

I guess this ticket can be closed then

@pablohashescobar pablohashescobar added the 🐛bug Something isn't working label Dec 7, 2023
@anmolsinghbhatia anmolsinghbhatia self-assigned this Dec 15, 2023
@sriramveeraghanta sriramveeraghanta linked a pull request Dec 15, 2023 that will close this issue
@pushya22
Copy link
Collaborator

#3141 This is fixed in this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants