Content
View differences
Updated by Jens Ulferts over 2 years ago
**As a** logged in user
**I want** These are just notes to select facilitate the sort order of project lists and persisted that selection implementation. The authoritative specification is in <mention class="mention" data-id="49687" data-type="work_package" data-text="#49687">#49687</mention>
**So that** I can optimize the information to display
### Acceptance criteria
* The user can choose When saving a view, the sort order in which to display projects within the "Configure view" modal (Implemented in #51671)
is persisted as well
### Technical notes
* Up to three sort criteria can be selected
* The user can still click on the Add order column header (json) to change the sort order. When doing so, the clicked on column will become the primary sort order, moving a previously clicked on column to be the second sort order. project\_queries table
* All columns with the exception of long text custom fields can be sorted by Handle (de)serialization
* The Send along sort order is persisted together with the filters and columns upon creation of a project list persisting
* When exporting Think about page wide state
* e.g. have local storage that is sent along with the list of projects (PDF forms or hidden html fields that are updated and XLS), then included in the sort order is adhered to form post
**I want**
**So that** I can optimize the information to display
### Acceptance criteria
* The user can choose
### Technical notes
* The user can still click on the
* All columns with the exception of long text custom fields can be sorted by
* The
* When exporting
* e.g. have local storage that is sent along with