Content
View differences
Updated by Rosanna Sibora 3 days ago
It's to be defined if we use the wording of "schemas" within OpenProject. The goal is to address the need users have. The concept for schemas in general need to be defined first.
Main goals:
* Deliver a concept in OpenProject that mirrors the core functionality of Jira Data Center's Workflow Schemes
* Allow administrators to create, manage, and assign workflow schemes across projects
* Ensure that different work package types within a project can follow different workflows
* Reduce repetitive manual configuration when setting up new projects
* Support large-scale enterprise deployments with hundreds of projects
* Concept must be flexible supporting various organizational cultures (centralized and federated structures)
* admins need the possibility to say if a schema can be overwritten by a project admin or not
* if a schema was overwritten by a project admin it cannot be updated via the global schema anymore (TBC)
Main goals:
* Deliver a concept in OpenProject that mirrors the core functionality of Jira Data Center's Workflow Schemes
* Allow administrators to create, manage, and assign workflow schemes across projects
* Ensure that different work package types within a project can follow different workflows
* Reduce repetitive manual configuration when setting up new projects
* Support large-scale enterprise deployments with hundreds of projects
* Concept must be flexible supporting various organizational cultures (centralized and federated structures)
* admins need the possibility to say if a schema can be overwritten by a project admin or not
* if a schema was overwritten by a project admin it cannot be updated via the global schema anymore (TBC)