Anthony

Gotcha, yeah that would be handy. We can add a new filter for the separate lookup expression instead, ie: https://beta.readthedocs.org/projects/test-builds/?version__icontains=build-tools- I think either the project or build filters have multiple...

Just noting that the UI that triggers a filtered version list already does this:  The issue here seems solely about linking users to list of versions with `icontains` lookups...

Yes, this UI is not meant to support multiple selection. I think the way to tie what you are looking for into the UI would be an explicit menu item...

I think the second task above is close already, we have some examples in the documentation already. Though we don't have anything mentioning PDF/etc, if we think that is strictly...

> I don't want to select multiple versions from the choice field I'm not describing selecting multiple versions in the version dropdown list, it's not the right element to use....

I think the next step here is probably just downgrading our Ngrok plan. It seemed like we could get by with just a single user plan or switching to the...

Unless Ngrok isn't doing something for us, swapping tunneling providers feels like a distraction. Ngrok seems to work fine for us, we're just not using it enough to justify paying...

I'll also add that the only time I ever find myself clicking on these links in the flyout is when I want to jump to the repo on GitHub, and...

Mmm good point. This does feel like a helpful feature for showing how fresh a version is, but not important enough to incur cache invalidation yet.

I had a similar question and these were the repos that I was thinking of. We did a fair amount of work to standardize these so seems useful to continue....