Content
View differences
Updated by Tobias Dillmann 27 days ago
> * Manage sprints
>
> * Allows adding and updating sprints
>
> * Allows adding and removing work packages (within sprint buckets)
>
> * Allows defining the order of work packages within the sprint bucket
>
> * Replaces the current "Update sprints"
>
> * Allows starting a new sprint
>
> * ~~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 starting a new sprint~~
>
> * ~~Allows completing an active sprint~~
>
> * View sprints
>
> * \[open\] copied from the epic. What is the permission necessary for? Seeing the sprint is definitely necessary whenever backlogs is to be used.
>
> * \[open\] There is an "Assign versions" permission that is required when wanting to connect work packages and versions. Do we want the same for sprints? This would allow a role like a "Product owner" in Scrum.
> Decision: To be covered by the 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.
* Additionally: <mention class="mention" data-id="71308" data-type="work_package" data-text="##71308">##71308</mention>
* Mappings of existing backlog permissions:
* View Master Backlog -> View Sprints
* View Taskboards -> to be merged into View Sprints
* Update Sprints -> Manage Sprints
>
> * Allows adding and updating sprints
>
> * Allows adding and removing work packages (within sprint buckets)
>
> * Allows defining the order of work packages within the sprint bucket
>
> * Replaces the current "Update sprints"
>
> * Allows starting a new sprint
>
> * ~~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 starting a new sprint~~
>
> * ~~Allows completing an active sprint~~
>
> * View sprints
>
> * \[open\] copied from the epic. What is the permission necessary for? Seeing the sprint is definitely necessary whenever backlogs is to be used.
>
> * \[open\] There is an "Assign versions" permission that is required when wanting to connect work packages and versions. Do we want the same for sprints? This would allow a role like a "Product owner" in Scrum.
> Decision: To be covered by the 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.
* Additionally: <mention class="mention" data-id="71308" data-type="work_package" data-text="##71308">##71308</mention>
* Mappings of existing backlog permissions:
* View Master Backlog -> View Sprints
* View Taskboards -> to be merged into View Sprints
* Update Sprints -> Manage Sprints