Content
View differences
Updated by Jens Ulferts over 2 years ago
**As a** logged These are just notes to facilitate the implementation. The authoritative specification is in user <mention class="mention" data-id="49687" data-type="work_package" data-text="#49687">#49687</mention>
**I want** to store, revisit and delete project lists (filters only)
**So that** I can organize projects for myself
### Acceptance criteria criteria
* Lists can be persisted under a name chosen by the user
* The filters are persisted.
* The following is not included
* columns (Implemented in #51670)
* sort order (Implemented in ...)
* Lists can be deleted via an entry in the "more" menu
* The user inserts the name of the list in a modal which also triggers the creation of the list (Subject to change later)
* Every logged in user can persist lists. By default, those Persisted lists will only be visible to the user creating the list. A user can be granted the permission to turn a list public and/or share it with other users.
* Persisted lists show up in the sidemenu from where they can be opened by clicking on them
* Only visible to the user having created the view (Sharing/Public implemented in ...)
* Sort list by name with the static ones on top
* No grouping (Implemented in ...)
* Whenever a list is opened (user Lists can be deleted
* Only filters can be persisted. Columns cannot be changed. Sort order ist not persisted or static),
### Technical notes
* Turn the page header displays the name of the opened list
BaseQuery into a module so that it can be included separately from having to inherit from AR::Base
* The static filter "All projects" is Have a separate module for unpersisted queries that all the default filter. Whenever rest of the project module is opened, this list is displayed, queries (e.g. members and users receive) so that the sidebar menu is highlighted interface works for columns and the header "All projects" displayed.
filters
* Besides Add the user persisted lists the sidebar has a fixed set of static lists: modules to every query
* "All projects": All projects that are active. This is the default list Create a database table:
* Use json column for persisting the index page data:
* filters
* "My projects": All active projects in which Add serialization for the current user is member
json columns
* "Archived projects": All projects not being active We need a specific json based serializer for this (other then the WP one)
* By status (there are Add a "Save" modal triggered by the more project statuses but those are not listed): menu
* "On track": All active projects having Persist filters
* Can include them in the status "On track"
modal via a hidden field
* "Off track": All active projects having the status "Off track" Ideally, work on global state, though
* "At risk": All active projects having Add a "Delete" item to the status "At risk"
menu if we loaded a persisted view
* The previously existing "Public projects" name of the list is to be removed.
displayed in the header
* The sidebar will not have a "+ Project" button any more ?Requires hard reload for now?
**I want** to store, revisit and delete project lists (filters only)
**So that** I can organize projects for myself
### Acceptance criteria
* Lists can be persisted under a name chosen by the user
* The filters are persisted.
* The following is not included
* columns (Implemented in #51670)
* sort order (Implemented in ...)
* Lists can be deleted via an entry in the "more" menu
* The user inserts the name of the list in a modal which also triggers the creation of the list (Subject to change later)
* Every logged in user can persist lists. By default, those
* Persisted lists show up in the sidemenu from where they can be opened by clicking on them
* Only visible to the user having created the view (Sharing/Public implemented in ...)
* Sort list by name with the static ones on top
* No grouping (Implemented in ...)
* Only filters can be persisted. Columns cannot be changed. Sort order ist not
### Technical notes
* Turn
* "All projects": All projects that are active. This is the default list
* Use json column
* filters
* "My projects": All active projects in which
* By status (there are
* "On track": All active projects having
* Can include them in
* "At risk": All active projects having