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

Tag list should be sorted #185

Closed
jamesnetherton opened this issue Aug 7, 2015 · 14 comments
Closed

Tag list should be sorted #185

jamesnetherton opened this issue Aug 7, 2015 · 14 comments
Labels

Comments

@jamesnetherton
Copy link

Hope this isn't a duplicate (didn't find anything similar)....

The list of image tags should be sorted into some logical order. E.g if I view the list of Debian image tags I get:

experimental    51 MB
rc-buggy    51 MB
wheezy-backports    35 MB
wheezy  35 MB
7   35 MB
7.8 35 MB
unstable    51 MB
testing 51 MB
stretch 51 MB
stable-backports

It'd be nicer if they were sorted to help find things quickly. Especially for images that have a lot of tags.

OS: Fedora 22
Browser: Chrome 44.0.2403.125

@ChristopherBiscardi
Copy link
Contributor

@jamesnetherton What sorting would be most useful to you? (alphabetical, recently pushed, size, etc).

@jamesnetherton
Copy link
Author

@ChristopherBiscardi For me personally, default sorting alphabetically. With the added option of sorting on any of the other tag attributes in ascending / descending order. Anything that makes it easy to find stuff is good.

@rantoniuk
Copy link

+1 for alphabetic sorting. Example of current messy sorting: https://hub.docker.com/r/cptactionhank/atlassian-jira/tags/

@posita
Copy link

posita commented Dec 4, 2015

What sorting would be most useful to you? (alphabetical, recently pushed, size, etc).

How about all of the above? The concept of multiple, sort-able columns has been around for quite a while, no? See also #415.

@jgkamat
Copy link

jgkamat commented Dec 4, 2015

I would prefer sorted by most recently pushed (if you can't give us a sorting option 😄), it makes more sense from a debug point of view (What if I want to delete that tag I just pushed (assuming we can delete tags eventually)).

@kristiehoward
Copy link

FYI @jgkamat #68 (ability to delete tags) was just deployed

@jgkamat
Copy link

jgkamat commented Dec 4, 2015

Oh nice, thanks!

@sshipway
Copy link

sshipway commented Feb 4, 2016

+1
I would prefer to be able to change the sort order between 'most recently pushed' and 'asciinumerically by tag'

Sorting ascibetically by tag is not good enough because 21.0 would cone before 3.1. The tag sort function needs to be able to sort intelligently so that latest comes first, and tags are split on '.' and '-' as separators, and parts matching /(v(er)?)[0-9]+/ are compared numerically. Might get a bit messy.

@rantoniuk
Copy link

Maybe this will be a good reference impl.

@chromerobv
Copy link

would love to be able to sort by recently pushed. any headway on this?

@ducttapecoder-vt
Copy link

/bump

The the lack of a 'sort by' or 'limit # on page' drop down makes viewing tags exceedingly difficult. Manually browsing through 28 pages of Confluence tags with 6.15.3 (the second most recent version) being on the last page is awful.

Sort options should be something like: alphabetical, age, 'asciinumerically' (as sshipway calls it), # of downloads, and some other attributes that don't seem to exist yet like FROM source or sub-tag (being able to filter for alpine seems so freaking logical it's sad it doesn't exist yet).

A simple search would also be amazing. Why after THREE YEARS are these features still not available?

@furiousassault
Copy link

Any update on this issue? Sorting by created timestamp might be very useful in self-maintained docker registry cleaning solutions.

@github-actions
Copy link

We are clearing up our old issues and your ticket has been open for 6 months with no activity. Remove stale label or comment or this will be closed in 15 days.

@sshipway
Copy link

Well, declaring the ticket stale is not quite as good as actually providing the feature, though both seem to result in the ticket being closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

10 participants