Content
View differences
Updated by Jens Ulferts 21 days ago
> * Backlogs needs to be activated for any of the permissions to work
>
> * View Manage sprints
>
> * Allows accessing backlogs adding and updating sprints
>
> * Allows seeing sprints on adding and removing work packages (once that feature is developed) (within sprint buckets)
>
> * Allows accessing defining the burndown chart order of work packages within the sprint bucket
>
> * This permission is a dependency for all Replaces the other permissions below. This is coded in. current "Update sprints"
>
> * Create sprints
>
> * Allows adding/updating/deleting sprints including name, dates but excluding status. Allows to configure whether to receive or to not receive shared sprints in the project configuration. starting a new sprint
>
> * Start/complete ~~Start and complete sprint (use case: this role would be relevant for SAFe teams or large organizations where sprints should be managed centrally. Interesting especially while sharing sprints.)~~
>
> * Allows changing the status of the sprint ~~Allows starting a new sprint~~
>
> * Manage sprint items
>
> * Allows adding and removing from a sprint, and re-ordering of items ~~Allows completing an active sprint~~
>
> * Share sprint View sprints
>
> * Allows \[open\] copied from the epic. What is the permission necessary for? Seeing the sprint is definitely necessary whenever backlogs is to configure sharing (all projects or sub-projects) in the project configuration be used.
>
> * Depends on \[open\] There is an "Assign versions" permission that is required when wanting to connect work packages and versions. Do we want the user having same for sprints? This would allow a role like a "Product owner" in Scrum.
> Decision: To be covered by the "Create sprints" Manage sprints permission.
>
<br>
Notes:
* Add Sprint permissions:
* Note that some permissions [already exist](https://github.com/opf/openproject/blob/7a17ee6b52f27b16498d8aa6d7d1700f4d98514a/modules/backlogs/lib/open_project/backlogs/engine.rb#L103). These will have to be considered for the migration, too.
* Manage sprints
* Allows adding and updating sprints
* Allows activating a sprint
* Replaces the current "Update sprints"
* Remove the "Assign versions" permission and use Manage Sprints instead.
* Mappings of existing backlog permissions:
* View Master Backlog -> View Sprints
* View Taskboards -> to be merged into View Sprints
* Update Sprints -> Manage Sprints
>
> * View
>
> * Allows accessing backlogs
>
> * Allows seeing sprints on
>
> * Allows accessing
>
> * This permission is a dependency for all
>
> * Create sprints
>
> * Allows adding/updating/deleting sprints including name, dates but excluding status. Allows to configure whether to receive or to not receive shared sprints in the project configuration.
>
> * Start/complete
>
> * Allows changing the status of the sprint
>
> * Manage sprint items
>
> * Allows adding and removing from a sprint, and re-ordering of items
>
> * Share sprint
>
> * Allows
>
> * Depends on
> Decision: To be covered by
>
Notes:
* Add Sprint permissions:
* Note that some permissions [already exist](https://github.com/opf/openproject/blob/7a17ee6b52f27b16498d8aa6d7d1700f4d98514a/modules/backlogs/lib/open_project/backlogs/engine.rb#L103). These will have to be considered for the migration, too.
* Manage sprints
* Allows adding and updating sprints
* Allows activating a sprint
* Replaces the current "Update sprints"
* Remove the "Assign versions" permission and use Manage Sprints instead.
* Mappings of existing backlog permissions:
* View Master Backlog -> View Sprints
* View Taskboards -> to be merged into View Sprints
* Update Sprints -> Manage Sprints