Begin of the insertion**As a** mobile app userEnd of the insertion Begin of the deletion **As** a \[enter role of user\]End of the deletion
**I want to** Begin of the insertionaccess a dedicated global search moduleEnd of the insertion Begin of the deletion \[enter objective\]End of the deletion
**so that** Begin of the insertionI can search across work packages and projects from one central place in the app.End of the insertion Begin of the deletion \[enter desired result\]End of the deletion

**Acceptance criteria**

* Begin of the insertionA dedicated “Search” entry point is available inEnd of the insertion Begin of the deletion \[TBD\] ShouldEnd of the deletion the Begin of the insertionmain navigation (e.g., bottom navigation bar) withEnd of the insertion Begin of the deletion global search andEnd of the deletion the work Begin of the insertiondone on <mention class="mention" data-id="71053" data-type="work_package" data-text="###71053">###71053</mention>.

* TappingEnd of the insertion Begin of the deletion packages tab beEnd of the deletion the Begin of the insertionsearch icon opens a full-screen global search module.End of the insertion Begin of the deletion same like in Wrike, Jira or Asana apps?End of the deletion

* Begin of the insertionTheEnd of the insertion Begin of the deletion Make work packageEnd of the deletion search Begin of the insertionmodule contains:

* A search input field with focus on open.

* Tabs for:

* Work packages

* Now work packages should be searchableEnd of the insertion by ID Begin of the insertionalso.

* Projects

* Projects have new filters for favorites, status and type.

* The module is independent from Home and other modules (no embedded search behavior).End of the insertion Begin of the deletion possible in the global search.End of the deletion

* Begin of the insertionWhen navigating back,End of the insertion Begin of the deletion Make searching projects possible inEnd of the deletion the Begin of the insertionuser returns to the previous module.End of the insertion Begin of the deletion global search.End of the deletion

* Begin of the insertionThe search state (query + selected tab + filters) is preserved duringEnd of the insertion Begin of the deletion \[TBD\] Include filters inEnd of the deletion the Begin of the insertionsame session unless explicitly cleared.

* TheEnd of the insertion Begin of the deletion globalEnd of the deletion search Begin of the insertionbar ofEnd of the insertion Begin of the deletion fromEnd of the deletion the home page Begin of the insertionopensEnd of the insertion Begin of the deletion or open directlyEnd of the deletion the Begin of the insertionnew separate search module.End of the insertion Begin of the deletion search.End of the deletion

* Begin of the insertionMimicEnd of the insertion Begin of the deletion \[TBD\] FindEnd of the deletion a Begin of the deletion way to mimic aEnd of the deletion similar behaviour to the recently viewed list on search Begin of the insertionopening.

* This will not sync with the recently viewed list of the search on the web app.

* We limit the recently viewed listEnd of the insertion Begin of the deletion opening (or decideEnd of the deletion to Begin of the insertion20 work packages.

End of the insertion Begin of the deletion wait until API implementation).

End of the deletion * Begin of the insertionWe need to storeEnd of the insertion Begin of the deletion \[TBD\] ReviewEnd of the deletion the Begin of the insertiondata per user and instance that is persisted even after logout.

* The widget onEnd of the insertion Begin of the deletion filters available inEnd of the deletion the Begin of the insertionhome page &quot;Recently edited&quot; also becomes &quot;Recently viewed&quot; with this logic.


End of the insertion Begin of the deletion global search.


End of the deletion **Technical notes**

* Begin of the insertionIntroduce a dedicated route/screen for Global Search.

* Search input should:

* Support debounced requests.

* Support clearing input (clear icon).

* Tab state and filter state should be maintained locally (state management solution depending on architecture).

* Ensure API endpoints support cross-entity querying (or separate calls per tab).

* Performance: Search requests must be optimized to avoid excessive calls.End of the insertion Begin of the deletion <br>End of the deletion


**Permissions and visibility considerations**

* Begin of the insertionAll authenticated users with permission to view at least one searchable entity (work packages, projects, time logs).End of the insertion Begin of the deletion _To whom is this feature visible?_End of the deletion

* Begin of the insertionTabs should only be visible if the user has permission for the respective entity.End of the insertion Begin of the deletion _When is it not visible?_End of the deletion


**Translation considerations**

* Begin of the insertionKey terms:

* Global search

* Search

* Work packages

* Projects

* Time logs

* Recently viewed

* Filters

* Status

* Type

* Project

* Log date


End of the insertion Begin of the deletion _Key terms and phrases in the key languages_&nbsp;


End of the deletion **Out of scope**

* Begin of the insertionAdvanced search operators (AND/OR, etc.)

* <mention class="mention" data-id="71053" data-type="work_package" data-text="###71053">###71053</mention>

* _Time logs (TBD)_

* _Time logs have new filters for log date and project._End of the insertion Begin of the deletion <br>


_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._End of the deletion