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
Is your enhancement related to a problem? Please describe.
For collection of sites using Distributor that have a large number of connected sites (e.g. >1000) there's a good option for searching through that listing on the Push menu to try and find a site to push content to. However the Pull Content menu lacks a similar search feature, so adding search there for the list of connected sites would be helpful in similar scenarios (e.g. >1000 connected sites).
Designs
Here's an example of the Push menu with ability to search for a connected site to push content to:
...and here's an example of how the Pull Content screen has no ability to search on connected sites, having something available would help for set ups that have 100s+ of connected sites to more quickly find the site to pull content from:
Describe alternatives you've considered
n/a
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Is your enhancement related to a problem? Please describe.
For collection of sites using Distributor that have a large number of connected sites (e.g. >1000) there's a good option for searching through that listing on the Push menu to try and find a site to push content to. However the Pull Content menu lacks a similar search feature, so adding search there for the list of connected sites would be helpful in similar scenarios (e.g. >1000 connected sites).
Designs
Here's an example of the Push menu with ability to search for a connected site to push content to:
...and here's an example of how the Pull Content screen has no ability to search on connected sites, having something available would help for set ups that have 100s+ of connected sites to more quickly find the site to pull content from:
Describe alternatives you've considered
n/a
Code of Conduct
The text was updated successfully, but these errors were encountered: