Content
View differences
Updated by Marc Alcobé 18 days ago
**As a** mobile OpenProject user **As** a \[enter role of user\]
**I want to** choose a default opening query for the Work packages module in my account settings \[enter objective\]
**so that** I always land on my preferred work package list when opening the module. \[enter desired result\]
#### **Acceptance Criteria** criteria**
<br>
* The account settings in the mobile app include a “Work packages settings” section.
* The “Work packages settings” section includes a “Defaults” group.
* The “Defaults” group includes a setting labeled “Default opening query”.
* Tapping “Default opening query” opens a selection bottom sheet listing only **default (built-in) queries** that are shared across projects.
* The selection screen lists the available Allow all default queries:
* All open
* Latest activity
* Recently created
* Overdue
* Created by me
* Assigned queries to me
* Shared with users
* Shared with me
* The current selection is clearly highlighted in the list.
* Selecting an item immediately updates the current selection and closes the selection bottom sheet.
* Returning to “Work packages settings” shows the chosen query be selected, as these are the value under “Default opening query”.
* If no selection was ever made (fresh install / new account), the default value is **All open**.
* When the user opens the Work packages module, the initial list shown uses the selected “Default opening query”.
* The selected query applies consistently regardless of which project the user is currently viewing (because only default queries are available).
* The setting is per user account (not per device) and is preserved across logout/login and app reinstall once the user signs only ones shared in again.
#### **Technical Notes**
<br>
* “Default queries” refers to OpenProject’s built-in, globally available work package queries that are not project-specific and are available consistently across all projects in the mobile app.
* The mobile app already has internal identifiers for these default queries (or can introduce them) so the selection can be stored stably independent of translation changes.
* Data model
* Persist Find a single user preference value, e.g. `work_packages.default_opening_query`.
* Store as an immutable identifier (string/enum), not as a translated label.
* API dependencies / contracts (OpenProject API v3)
* Preference storage can way to be implemented either:
* As able to select a dedicated user preference field served by the API (preferred for cross-client consistency), or
* Via an existing user “settings/preferences” mechanism if one exists in the current product architecture.
* The work package list retrieval must support applying the corresponding default query/filter (either by query id, filter payload, or a known built-in query key). If the API relies favorite view (1st on query resources that are project-scoped, the mobile app must instead apply equivalent filter definitions that are valid across contexts.
each project?)
**Technical notes**
* Performance and caching
* Cache the preference locally to avoid delaying initial navigation; refresh in background after login/when settings screen is opened.
* Ensure that switching the setting does not require reloading the entire settings hierarchy; only update the value row.
#### <br>
**Permissions and Visibility Considerations** visibility considerations**
<br>
* The setting _To whom is visible to any signed-in user of the mobile app. this feature visible?_
* The setting does _When is it not expose any project-specific or restricted data because only global default queries are selectable.
* The resulting initial list still respects all existing permission checks:
* Users only see work packages they are allowed to view.
* If a chosen query implies filters like “Assigned to me” or “Created by me”, it must still only return items the user can access.
#### visible?_
**Translation Considerations** considerations**
* New strings:
* `Defaults opening query`
* `Define the defaults of work packages views _Key terms and phrases in the app.`
* `Default opening query`
* The stored preference value must NOT be translated. key languages_
#### **Out of Scope** scope**
* Selecting project-specific saved queries (custom queries) as the default opening query.
* Creating, editing, or managing queries from the mobile app settings.
* Per-project default opening query behavior.
* Changes <br>
_Set the_ **To be informed/consulted teams** _field to the existing Work packages settings options unrelated include all teams necessary to this feature (e.g., be informed of the “Automatically mark all as read”, “Mark all as read when comment”, “Mark as read on reply”, or “Cancel creation warning” settings beyond visual grouping/layout consistency). changes._
**I want to** choose a default opening query for the Work packages module in my account settings
**so that** I always land on my preferred work package list when opening the module.
#### **Acceptance Criteria**
<br>
* The account settings in the mobile app include a “Work packages settings” section.
* The “Work packages settings” section includes a “Defaults” group.
* The “Defaults” group includes a setting labeled “Default opening query”.
* Tapping “Default opening query” opens a selection bottom sheet listing only **default (built-in) queries** that are shared across projects.
* The selection screen lists the available
* All open
* Latest activity
* Recently created
* Overdue
* Created by me
* Assigned
* Shared with users
* Shared with me
* The current selection is clearly highlighted in the list.
* Selecting an item immediately updates the current selection and closes the selection bottom sheet.
* Returning to “Work packages settings” shows the chosen query
* If no selection was ever made (fresh install / new account), the default value is **All open**.
* When the user opens the Work packages module, the initial list shown uses the selected “Default opening query”.
* The selected query applies consistently regardless of which project the user is currently viewing (because only default queries are available).
* The setting is per user account (not per device) and is preserved across logout/login and app reinstall once the user signs
#### **Technical Notes**
<br>
* “Default queries” refers to OpenProject’s built-in, globally available work package queries that are not project-specific and are available consistently across
* The mobile app already has internal identifiers for these default queries (or can introduce them) so the selection can be stored stably independent of translation changes.
* Data model
* Persist
* Store as an immutable identifier (string/enum), not as a translated label.
* API dependencies / contracts (OpenProject API v3)
* Preference storage can
* As
* Via an existing user “settings/preferences” mechanism if one exists in the current product architecture.
* The work package list retrieval must support applying the corresponding default query/filter (either by query id, filter payload, or a known built-in query key). If the API relies
**Technical notes**
* Cache the preference locally to avoid delaying initial navigation; refresh in background after login/when settings screen is opened.
* Ensure that switching the setting does not require reloading the entire settings hierarchy; only update the value row.
####
<br>
* The setting
* The setting does
* The resulting initial list still respects all existing permission checks:
* Users only see work packages they are allowed to view.
* If a chosen query implies filters like “Assigned to me” or “Created by me”, it must still only return items the user can access.
####
* New strings:
* `Defaults opening query`
* `Define the defaults of work packages views
* `Default opening query`
* The stored preference value must NOT be translated.
#### **Out of Scope**
* Selecting project-specific saved queries (custom queries) as the default opening query.
* Creating, editing, or managing queries from the mobile app settings.
* Per-project default opening query behavior.
* Changes
_Set the_ **To be informed/consulted teams** _field