Content
View differences
Updated by Max Mutzge about 5 years ago
_The feature request for a global default view (i.e. for all projects) can be found here: <mention class="mention" data-id="31423" data-type="work_package" data-text="#31423">#31423</mention>_
**As** a project manager and team member
**I want to see** my saved custom view as the default view when first clicking on "Work Packages"
**so that** the default view is more relevant for me instead of having to additionally scroll through the views to select the one I need to begin with as the default "All Open" view not optimal.
**Scenario 1- Setting the default public view for a project.**
A user with project admin, global administrator rights, or Users with the 'Manage public views' permission can set a saved _**public**_ view as the default view for the project.
Set by:
1. Create and save the new customised view with Public access.
2. Set the "Project Default View" to true..
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/20974/content"></div></figure>
The result will be that any member of the project without a custom default view set will first be shown this public view when they enter the "Work Packages" module of the project.
The option will be disabled if the "public" setting is not checked.
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/20975/content"></div></figure>
**Scenario 2- Setting the default custom view.**
A user can set one of their private custom views as the default view for the project.
Set by:
1. Create and save the new customised view.
2. Set the "Default View"
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/20977/content"></div></figure>
The result will be that the custom view will be the first (default) view that is shown when the user first visits the Work Packages page of the project.
This will be the view shown for the user, even if any a project default view has been set by admin.
**Acceptance criteria**
* a member is able to set a custom view as their default view for the given project.
* a member default view set will take precedence over any set project level default view for the respective user
* a member is able to unset a custom view from being the default view for the given project so that default will either be the project set view or "All open" if one is not set (current default).
* If a user default view or the project default view is not set, it will default to the current "All open" default view.
* the view must be public to be set as the default project view for its members (by reason).
* members with given permissions (project admin, global administrator rights, or Users with the 'Manage public views' permission) can set a saved (public) view as the default project view for the project
**As** a project manager and team member
**I want to see** my saved custom view as the default view when first clicking on "Work Packages"
**so that** the default view is more relevant for me instead of having to additionally scroll through the views to select the one I need to begin with as the default "All Open" view not optimal.
**Scenario 1- Setting the default public view for a project.**
A user with project admin, global administrator rights, or Users with the 'Manage public views' permission can set a saved _**public**_ view as the default view for the project.
Set by:
1. Create and save the new customised view with Public access.
2. Set the "Project Default View" to true..
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/20974/content"></div></figure>
The result will be that any member of the project without a custom default view set will first be shown this public view when they enter the "Work Packages" module of the project.
The option will be disabled if the "public" setting is not checked.
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/20975/content"></div></figure>
**Scenario 2- Setting the default custom view.**
A user can set one of their private custom views as the default view for the project.
Set by:
1. Create and save the new customised view.
2. Set the "Default View"
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/20977/content"></div></figure>
The result will be that the custom view will be the first (default) view that is shown when the user first visits the Work Packages page of the project.
This will be the view shown for the user, even if any a project default view has been set by admin.
**Acceptance criteria**
* a member is able to set a custom view as their default view for the given project.
* a member default view set will take precedence over any set project level default view for the respective user
* a member is able to unset a custom view from being the default view for the given project so that default will either be the project set view or "All open" if one is not set (current default).
* If a user default view or the project default view is not set, it will default to the current "All open" default view.
* the view must be public to be set as the default project view for its members (by reason).
* members with given permissions (project admin, global administrator rights, or Users with the 'Manage public views' permission) can set a saved (public) view as the default project view for the project