Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-4765

Make Find Bar configurable via YAML

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Neutral Neutral
    • 6.1.4, 6.2
    • None
    • None
    • None
    • Yes
    • UI Framework 11
    • 5

      User story:

      My site deals heavily with assets. I want to see assets higher in results because I work with them often.

      My site doesn't use Stories very often. I want to demote them in the Suggestions order.

      I have a custom app Products that is very important for my users. I want to make it higher in Suggestions.

      The default group ordering (MGNLUI-4728) doesn't know what is important to users on a particular site. For example, Assets are in place #5 which may be too low. Make it easier for a practitioner to change the category order through configuration, for example via YAML.

      Business benefit: Relevance. Content types that are important to your daily work are listed first.

      Acceptance criteria:

      • A system admin can configure the group order.
      • A system admin can configure the number of suggestions & results in each group.
      • A system admin can configure the find bar to include/exclude specific user realms as last editors (see MGNLUI-5523)
      • Configuration is in a YAML file.
      • A developer can deploy new Magnolia sites with the correct group order.
      • Consider making everything in the Find Bar class configurable without having to touch code.

        Acceptance criteria

              rkovarik Roman Kovařík
              ahietala Antti Hietala
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Task DoD

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0d
                    0d
                    Logged:
                    Time Spent - 2h 44m
                    2h 44m