Uploaded image for project: 'Repository'
  1. Repository
  2. REPO-2169

Query APIs should not require a minimum number of characters in the term

    Details

      Description

      In REPO-2111 I've raised the requirement to make it possible to provide filtering on all list APIs... at the moment this is really only possible in the query APIs (i.e. /queries/people).

      However there is a fundamental problem with these APIs in that they require a minimum of 2 characters in the search term otherwise they return a 400 response.

      The problem here is when you want to use these queries in a form control with type ahead filtering. A concrete example of this would be a multi-select or filtering select box where you can select a user.

      It is impossible to use the APIs in this scenario because the initial characters will be have to be ignored (resulting in a bad UX). As a user I want to be able to immediately begin filtering on a single character and I want all results returned when no characters are entered.

      Please remove this restriction from the queries and don't add it to any other filtering capabilities.

        Attachments

          Issue Links

            Structure

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  ddraper David Draper [X] (Inactive)
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel