Uploaded image for project: 'Nuxeo Studio'
  1. Nuxeo Studio
  2. NXS-4842

Allow users to search for things to switch to (UI)

    XMLWordPrintable

    Details

    • Type: User story
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 73.18
    • Component/s: Ergonomy & UX

      Description

      As a / an Studio user I want to Get suggestions based on what I type in the quick switcher and navigate to it upon selection so that I can browse my project quickly
      As a / an Studio user I want to See options grouped by type (features, menus, resources) so that I can easily browse the suggestions list
      As a / an Studio user I want to See options ordered by name in ascending order for each group so that I can easily browse the suggestions list

      See also NXS-4765 Allow users to search for things to switch to (REST API)

      ________

      Given I am in a Studio project
      When Typing in the text box
      Then Suggestions are offered based on my input:

      • case insensitive
      • feature / menu / resource name should contain the input, not start with it

      ________

      Given I am in a Studio project
      When Typing in the text box
      Then The following are offered because indexed:

      Modeler
      Menu names
      Last level, e.g. index ""schemas"" but not “content model”, “Event Handlers” but not “Automation”
      We might still want to show the upper level, for instance to help with registries vs automatic registries but not make a search on it
      => Should point to the corresponding url without reloading the project
      Feature ids
      We want to take people to the feature but not the tabs inside it
      e.g. we can take people to the “toto” doctype but not the “creation layout” tab of it if JSF UI is activated
      => Should point to the feature directly
      Branch names
      => Should open branches list
      Resources:
      Images
      Schemas (uploaded as xsd files)
      Vocabularies (uploaded as csv files)
      => Should open the resources page
      Designer
      Menu entries
      Custom contributions names
      name for custom document pages, left menu items, main menu pages, actions, themes
      File names (e.g. nuxeo-toto-create-layout.html)
      For all layouts (doctype, workflow, pp)
      => should point to the editor
      For translation files (messages*.json) / i18n files in modeler
      => Should point to the editor for designer
      => should point to the resources for modeler
      File names for custom elements?
      => Should point to the file edition
      ______

      Given I am in a Studio project
      When Typing in the text box
      Then The following are NOT offered because NOT indexed:

      Modeler
      Releases names
      Tag names
      Tabs inside features
      Features content
      Designer
      Default contributions
      Features content
      _______

      Given I am in a Studio project
      When Typing in the text box
      Then Suggested features depend on my package selection: for instance I am offered JSF UI menu options only if JSF UI is in my dependencies
      _______

      Given I am in a Studio project
      When Typing in the text box
      Then I see the suggestions as
      [Feature menu] [Feature name] for features
      [Menu name] for menus
      [Resource name] for resources

      _______

      Given I am in a Studio project
      When Typing in the text box
      Then For each option group, suggestions are ordered in alphabetical order asc

      ______

      Given I am in a Studio project
      When Typing in the text box
      Then Options are grouped into:
      Features first
      Menus second
      Resources third

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 4 days, 2 hours
                  4d 2h