You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
I'd like to revisit that pattern and tune up what we're using those labels for.
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.
The project version listing currently defaults to
recently built
sorting, which helps some, but does hide important versions likelatest
/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.
The text was updated successfully, but these errors were encountered: