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

Projects: add better default sorting to version listing #11510

Open
2 tasks
agjohnson opened this issue Aug 2, 2024 · 4 comments
Open
2 tasks

Projects: add better default sorting to version listing #11510

agjohnson opened this issue Aug 2, 2024 · 4 comments
Labels
Accepted Accepted issue on our roadmap Improvement Minor improvement to code

Comments

@agjohnson
Copy link
Contributor

The project version listing currently defaults to recently built sorting, which helps some, but does hide important versions like latest/stable.

I had originally tried to add a sort by relevance sorting method, but felt I was hacking up the queryset too much. But it seems really doable and would be better default UX.

I brought this up in this issue as a way to surface latest/stable higher in the version list. But either way I think it would be a better default sorting, regardless of what we do with a button.

And to clarify, this will not alter any other filter querysets.

  • Add a new project version sorting method, sort by relevance. This would be sort by recently built, plus latest/stable first in the query.
  • Use this as the default sorting method on the version listing view.
@agjohnson agjohnson added Improvement Minor improvement to code Accepted Accepted issue on our roadmap labels Aug 2, 2024
@agjohnson agjohnson added this to the Dashboard minor bugs milestone Aug 2, 2024
@humitos
Copy link
Member

humitos commented Aug 5, 2024

This would be sort by recently built, plus latest/stable first in the query.

I would probably say "Default version", Latest and Stable. That way, it's easier to find the actual default version first.

Also, I would suggest to distinct visually these 3 from the rest of the items. Maybe a different block?

@agjohnson
Copy link
Contributor Author

agjohnson commented Aug 5, 2024

There are some options here, yeah.

I wouldn't move these to separate block or style the rows different. I'd like to retain the same UI listing and pagination look and feel in a consistent manner across all UIs.

But we could color the version's buttons primary to make those rows stand out, and there is already a pattern for using labels to describe special version states:

image

I'd like to revisit that pattern and tune up what we're using those labels for.

@humitos
Copy link
Member

humitos commented Aug 6, 2024

Actually, using a different color for the "Default" label would be a great first step to me 👍🏼

@agjohnson
Copy link
Contributor Author

Yeah, that's what I was thinking too. Matching colors on the buttons and labels, should be a fair amount of visual distinction already. I'd still like to see them at the top of the list to further help identify them as important versions, but both in combination sounds like much better UX.

We can do the color changes separate, that's an easier change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accepted Accepted issue on our roadmap Improvement Minor improvement to code
Projects
None yet
Development

No branches or pull requests

2 participants