[MGNLPER-38] Provide SearchResultSuppliers for JCR workspaces Created: 27/Jul/18  Updated: 26/Feb/20  Resolved: 01/Nov/18

Status: Closed
Project: Periscope
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: New Feature Priority: Neutral
Reporter: Cedric Reichenbach Assignee: Ilgun Ilgun
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 49m
Original Estimate: Not Specified

Issue Links:
Problem/Incident
causes MGNLPER-75 Autogenerated JcrSearchResultSupplier... Closed
Relates
relates to CONTEDIT-191 SearchResultSupplier for Stories Closed
relates to MGNLDEMO-299 SearchResultSupplier for Tours Closed
relates to MGNLPER-63 Make properties searchable in config ... Closed
dependency
is depended upon by DOCU-1685 Update references to "search" in the ... Closed
Template:
Acceptance criteria:
Empty
Documentation update required:
Yes
Epic Link: Periscope back-end MVP
Sprint: Basel 159
Story Points: 8

 Description   

Search result suppliers for all (at least magnolia-native) workspaces should be in place.

Acceptance criteria:

  • All Magnolia native workspaces are searchable with Find Bar.

There are two possible approaches:
1. Each module introducing a workspace also configures a corresponding result supplier, e.g. -magnolia-travel-tours comes with a supplier for the tours workspace.-
2. We detect workspaces after startup and create corresponding suppliers on-the-go.


Generated at Mon Feb 12 10:28:07 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.