-
Bug
-
Resolution: Done
-
Major
-
2.1.3, 2.2.1, 2.3
-
None
-
False
-
-
False
-
Fixed an issue when imports contained more than 100 namespaces.
-
Release Note
Description
If you have over 100 namespaces in automation hub, the UI won't display imports for any namespaces that aren't listed in the first 100 namespaces that are created in the system.
It looks like the UI tries to load 1000 namespaces from the API, and only gets back 100 and ignores pagination beyond that point.
Right now the UI only lets me select from a dropdown with the first 100 namespaces in the system. The UI should be updated with a more sensible filter like the one on the remote registry form that allows them to search for a namespace and pick one from a list of drop downs:
Key Dependency Versions
4.6 (this is probably a bug since 4.2, but I'm too lazy to check)
Steps to Reproduce
Create 101 namespaces. Attempt to import a collection into the 101st namespace.
Actual Behavior
I can't select any namespaces past the 100th one created.
Expected Behavior
I should be able to filter the list of namespaces available to me with a text search.
- mentioned on