Content
View differences
Updated by Marc Alcobé about 1 year ago
**As** a mobile app user
**I want to** be able to sort and search the work packages I'm seeing
**so that** I can find the work package I'm looking for easily
**Acceptance criteria**
* The default sorting order matches the sorting used in the web app for that view/query.
* Add a new sub-header toolbar on top of the work package list, including a search bar and sort icon button.
* Add a divider between the project and view selection and the new sub-header bar.
* Search functionality:
* Tapping on the search icon button will expand a full width search bar in a focus state and open the keyboard.
* Users will be able to input and search by subject and ID.
* The scope of the search should only be the work packages in the current project and view/query.
* If there are no matching results, display an empty status.
* Users can always cancel the search using the "X" (that also clears the input text) button or by navigating somewhere else in the app.
* If the user leaves mid-search and come back to the same view, the content of the view is restored without search bar.
* Search after opening a work package should be cleared and reset the default of the query.
* If there is a sorted override in the current view and the user taps on search, the content below the search while not typing anything should be the sorted one.
* Sort by functionality:
* Tapping on the sort icon button opens a dropdown modal with the options:
* ID
* Subject
* Type
* Status
* Latest edited
* Latest commented
* Latest created
* After the user selected the sorting criteria to apply, the list below will be ordered by that criteria alphabetically (e.g. Type: 1st BUG then FEATURE).
* If the user leaves the page and come back to the same view, the default order of the view is restored.
* Sorting order when closing a work package opened form a sorted list should be persisted.
* When the user taps on any of the sorting options, this sorts the current view descending. The icon is updated from the sort icon to the sort descending one.
_\[tbs\] Ascending, descending, remove_
* If then the user opens the sorting modal again and taps on the same sorting order, the order will switch from descending to ascending. The _\[tbs\] Change of icon on the icon button change once again to ascending.
* If the user opens the sorting modal and taps once more on the same option, the sorting will be removed. Icon will go back to the sorting default icon.
when used_
**Visuals**
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/434941/content"> <img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/434942/content"> <img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/434943/content">
**Technical notes**
* <br>
**Permissions and Visibility considerations**
* Make the functionalities available to everyone, as views can't be saved from mobile app.
**Out of scope**
* Save any new view/query out of the new sorting order or search results.
* Change the default sort ordering of a view by saving.
**I want to** be able to sort and search the work packages I'm seeing
**so that** I can find the work package I'm looking for easily
**Acceptance criteria**
* The default sorting order matches the sorting used in the web app for that view/query.
* Add a new sub-header toolbar on top of the work package list, including a search bar and sort icon button.
* Add a divider between the project and view selection and the new sub-header bar.
* Search functionality:
* Tapping on the search icon button will expand a full width search bar in a focus state and open the keyboard.
* Users will be able to input and search by subject and ID.
* The scope of the search should only be the work packages in the current project and view/query.
* If there are no matching results, display an empty status.
* Users can always cancel the search using the "X" (that also clears the input text) button or by navigating somewhere else in the app.
* If the user leaves mid-search and come back to the same view, the content of the view is restored without search bar.
* Search after opening a work package should be cleared and reset the default of the query.
* If there is a sorted override in the current view and the user taps on search, the content below the search while not typing anything should be the sorted one.
* Sort by functionality:
* Tapping on the sort icon button opens a dropdown modal with the options:
* ID
* Subject
* Type
* Status
* Latest edited
* Latest commented
* Latest created
* After the user selected the sorting criteria to apply, the list below will be ordered by that criteria alphabetically (e.g. Type: 1st BUG then FEATURE).
* If the user leaves the page and come back to the same view, the default order of the view is restored.
* Sorting order when closing a work package opened form a sorted list should be persisted.
* When the user taps on any of the sorting options, this sorts the current view descending. The icon is updated from the sort icon to the sort descending one.
* If the user opens the sorting modal and taps once more on the same option, the sorting will be removed. Icon will go back to the sorting default icon.
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/434941/content"> <img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/434942/content"> <img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/434943/content">
**Technical notes**
* <br>
**Permissions and Visibility considerations**
* Make the functionalities available to everyone, as views can't be saved from mobile app.
**Out of scope**
* Save any new view/query out of the new sorting order or search results.
* Change the default sort ordering of a view by saving.