[MGNLUI-4929] Allow users to turn biasing results from the current app off Created: 20/Dec/18  Updated: 21/Jan/19  Resolved: 10/Jan/19

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

Type: Story Priority: Neutral
Reporter: Simon Lutz Assignee: Cedric Reichenbach
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 1h
Time Spent: 6.5h
Original Estimate: Not Specified

Attachments: PNG File app_specific_results.png     PNG File filters.png     PNG File global_results.png    
Issue Links:
dependency
depends upon MGNLUI-4921 Bias results from the current app in ... 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
Date of First Response:
Epic Link: Search relevance
Sprint: Foundation 1, Foundation 2
Story Points: 0.5

 Description   

The story MGNLUI-4921 introduced having the group of results from the current app on top of the list and highlighted rather than having a filter set automatically. While this is beneficial for the mentioned reasons, it makes it impossible to return to a regular global search with one click.

User story:

As a user, I want to be able to disable the biasing of results from the current app with one click.

Acceptance criteria:

  • Search from an app, see results, one click to remove the biasing of results from the current app
  • Default: results are biased (checkbox ticked)
  • Visuals: according to design (avongunten could you please provide the screen?), text should be "Show results from current app first"
  • Once the user filters for a specific result type, this checkbox becomes irrelevant and should disappear
  • The checkbox value should be sticky and remain for the next search executed also when started from a different app

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