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
This might be a feature request. In any case, the UX as it stands is confusing to me.
Repro:
select any report queue
enter a search string
Expected:
filter the report queue for matches on the search string
Actual:
empty list in the queue
afai can tell the HTTP request https://my-service-url/reports?term=mystring#
would trigger searchActors/searchPosts as if you'd typed the search string into the public API. Response time and other UX observations support this hypothesis.
Under the covers I expect the search always works OK, but there is no logic to leverage the result set to provide a filtered view of report queues.
If there is a different way to filter report queues to a subset of accounts using content search, that would be great. As it stands I'm about to add automation to trawl our pending reports and add Tags to routing.
The text was updated successfully, but these errors were encountered:
This might be a feature request. In any case, the UX as it stands is confusing to me.
Repro:
Expected:
Actual:
afai can tell the HTTP request https://my-service-url/reports?term=mystring#
would trigger searchActors/searchPosts as if you'd typed the search string into the public API. Response time and other UX observations support this hypothesis.
Under the covers I expect the search always works OK, but there is no logic to leverage the result set to provide a filtered view of report queues.
If there is a different way to filter report queues to a subset of accounts using content search, that would be great. As it stands I'm about to add automation to trawl our pending reports and add Tags to routing.
The text was updated successfully, but these errors were encountered: