Content
View differences
Updated by Jens Ulferts over 1 year ago
**As** a project administrator \[enter role of user\]
**I want to** select the active stages/gates of my project from the list of stages/gates defined for the instance \[enter objective\]
**so that** I can deviate from the default to reflect the process in place in my project. \[enter desired result\]
Assumes ###58159 is done.
**Acceptance criteria**
* A new menu is added to the project menu in below the "Project settings" labeled "Gates and Stages"
* It looks and behaves similar to the project attributes administration.
* \[open\] The exact visualization of the administration.
* To see and access the project administration a permission is required.
* \[open\] What is the name of the permission?
* \[Assumption\] - Roles having the 'edit project' permission will receive the new permission both when seeding and when migrating.
* Within this administration, all currently existing stages and gates are listed.
* The name and type (stage/gate) is displayed.
* The type (rhombus for gate, arrow for stage) are displayed in the color defined for the stage/gate.
* They are listed in the order defined in the instance administration.
* \[Assumption\] - The order cannot be changed.
* The project administrator can activate and deactivate a gate/stage.
* Disabled stages/gates will not be displayed:
* In the overview page
* In the project list (see ##58160)
* A project will also not match a filter for a stage/gate if the project has that stage/gate disabled.
* In work packages having the stage/gate associated (see ##58162)
* \[Assumption\] - The work package journal will not show gates/journals that are disabled.
* \[Assumption\] - Filters will not find a work package with a disabled stage/gate.
* Upon copying a project, the active/disabled state of it's gates/stages is copied along.
* \[open\] Should the functionality be capsulated in a project module which would allow to completely deactivate the functionality for a project?
* \[open\] Should this be available via the API v3?
**I want to** select the active stages/gates of my project from the list of stages/gates defined for the instance
**so that** I can deviate from the default to reflect the process in place in my project.
Assumes ###58159 is done.
**Acceptance criteria**
* A new menu is added to the project menu in below the "Project settings" labeled "Gates and Stages"
* It looks and behaves similar to the project attributes administration.
* \[open\] The exact visualization of the administration.
* To see and access the project administration a permission is required.
* \[open\] What is the name of the permission?
* \[Assumption\] - Roles having the 'edit project' permission will receive the new permission both when seeding and when migrating.
* Within this administration, all currently existing stages and gates are listed.
* The name and type (stage/gate) is displayed.
* The type (rhombus for gate, arrow for stage) are displayed in the color defined for the stage/gate.
* They are listed in the order defined in the instance administration.
* \[Assumption\] - The order cannot be changed.
* The project administrator can activate and deactivate a gate/stage.
* Disabled stages/gates will not be displayed:
* In the overview page
* In the project list (see ##58160)
* A project will also not match a filter for a stage/gate if the project has that stage/gate disabled.
* In work packages having the stage/gate associated (see ##58162)
* \[Assumption\] - The work package journal will not show gates/journals that are disabled.
* \[Assumption\] - Filters will not find a work package with a disabled stage/gate.
* Upon copying a project, the active/disabled state of it's gates/stages is copied along.
* \[open\] Should the functionality be capsulated in a project module which would allow to completely deactivate the functionality for a project?
* \[open\] Should this be available via the API v3?