[MGNLUI-4728] Predictable result category order Created: 19/Oct/18  Updated: 09/Nov/18  Resolved: 05/Nov/18

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0

Type: Improvement Priority: Neutral
Reporter: Cedric Reichenbach Assignee: Cedric Reichenbach
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLUI-4765 Make Find Bar configurable via YAML Closed
Relates
relates to MGNLPER-39 Support cross-supplier search and ran... Closed
relates to MGNLPER-57 Remove documentation website from Fin... Closed
dependency
depends upon MGNLPER-52 Support async execution of result sup... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Documentation update required:
Yes
Epic Link: Find Bar front-end MVP
Sprint: Basel 159
Story Points: 3

 Description   

Currently, the order in which suppliers are listed in the result view is random (that is, based on a race condition).

Instead, order should be deterministic.

Acceptance criteria

  • Results order:
    1. Apps
    2. Top hits
    3. Pages
    4. Stories
    5. Assets
    6. Tours
    7. <any custom result supplier in alphabetical order>
  • Order of suppliers should be configurable, e.g. through FindBarConfiguration, or through a priority flag on each supplier.

Generated at Mon Feb 12 09:19:29 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.