Content
View differences
Updated by Niels Lindenthal 4 months ago
# Individual configuration of states and workflows
**As** a OP project-admin
**I want to** configure the states and the workflows of every project individual
**so that** I can setup projects individual for the customer proccesses and needs.
For example, a small internal project can have a simpler and have a more open configuration than a large customer project.
## Workaround
Create the same state e.g. "in progress" for every project in the admin area. "in progress (customer)" "in progress (company)"
* bad integration with linked projects (reference, copy a task)
* messy configuraiton
## **Acceptance criteria**
* Add the same configuration in the porject-settings as in the system administration.
* The The navigation menu item "Work package types" will be found as a child element "Types" in the group "Work packages"
* The configuration states and workflows are also included in the Group "Work packages", implemented as in the administration area
<img class="image_resized op-uc-image op-uc-image_inline" style="width:255px;" src="/api/v3/attachments/200060/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/200061/content"><img class="image_resized op-uc-image op-uc-image_inline" style="width:241px;" src="/api/v3/attachments/200062/content">
* If a new project is created the project will copy the default configuration of the administration
* If a new project is created with a other project as a template the project will copy the configuration of the template project
* The configuration in the project overwrites the configuration of the administration with its individual changes, for each status or workflow separately.
* Therefore if a state is changed to "read-only" in the project-settings, this state is now overwriten by the project.
* If the state is not changed by the project-settings, you can still change it globally in the admin area.
* if a custom-project state is created, the connection to the original admin state should be stored.
* the projects should still be integrated nicely e.g. you can copy a task into a other project with a custom state.
<br>
**As** a OP project-admin
**I want to** configure the states and the workflows of every project individual
**so that** I can setup projects individual for the customer proccesses and needs.
For example, a small internal project can have a simpler and have a more open configuration than a large customer project.
## Workaround
Create the same state e.g. "in progress" for every project in the admin area. "in progress (customer)" "in progress (company)"
* bad integration with linked projects (reference, copy a task)
* messy configuraiton
## **Acceptance criteria**
* Add the same configuration in the porject-settings as in the system administration.
* The
* The configuration states and workflows are also included in the Group "Work packages", implemented as in the administration area
<img class="image_resized op-uc-image op-uc-image_inline" style="width:255px;" src="/api/v3/attachments/200060/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/200061/content"><img class="image_resized op-uc-image op-uc-image_inline" style="width:241px;" src="/api/v3/attachments/200062/content">
* If a new project is created the project will copy the default configuration of the administration
* If a new project is created with a other project as a template the project will copy the configuration of the template project
* The configuration in the project overwrites the configuration of the administration with its individual changes, for each status or workflow separately.
* Therefore if a state is changed to "read-only" in the project-settings, this state is now overwriten by the project.
* If the state is not changed by the project-settings, you can still change it globally in the admin area.
* if a custom-project state is created, the connection to the original admin state should be stored.
* the projects should still be integrated nicely e.g. you can copy a task into a other project with a custom state.
<br>