[MGNLUI-4676] Find Bar search is configured by admin for groups and roles Created: 10/Jul/18  Updated: 06/Oct/22  Resolved: 06/Oct/22

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

Type: Story Priority: Neutral
Reporter: Anja von Gunten Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MGNLUI-4677 Find Bar search is configured by indi... Closed
dependency
depends upon MGNLUI-4765 Make Find Bar configurable via YAML 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)
Date of First Response:

 Description   

In general, we can rely on standard Magnolia permissions and roles to show relevant results to users. However, the improvements in this ticket make it easier for a site admin to configure Find Bar. For example, if you use Amazon S3 connector for assets you may want to exclude those assets from Find Bar search for a particular user group.

User story:

As an admin, I want to configure which apps to search, so that results match ideally for roles and groups. 

Acceptance criteria:

  • Find Bar configuration is done in a single place.
  • Only admin configures the results.
  • Configuration applies to all users on the site.
  • Configuration can be done per group and role, but not per individual user.
  • Find Bar configuration is done in the Find Bar config file or similar, and not by GUI.
  • Sensible default is provided: Pages, Tours, Stories, Assets.

Background: Since we don't have a search box in each app anymore in Resurface UI, we need the option to search through all 30 workspaces. Clients should be able to configure which workspaces to search, including any workspaces of their own.


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