# Epic FND-70 - Project "flavours" to combine and manage various configuration groups centrally

Project: Stream workspace foundations
Status: new
URL: https://community.openproject.org/work_packages/FND-70

## Detailed specification

### Motivation and background information

### Acceptance criteria

*   As an admin I can modify a project flavour centrally and all project having that flavour will be updated.
    
*   I cannot overwrite/undo on a project level what was set via a flavour.
    
*   I can say per flavour which project attribute shall be switched on (I cannot say which shall be switched off)
    
*   I can say per flavour which work package custom fields shall be switched on (I cannot say which shall be switched off)
    
*   I can say per flavour which work package types shall be enabled (I cannot say which shall be switched off)
    
*   I can say per flavour which modules shall be enabled (I cannot say which shall be switched off)
    
*   I can set the field context of custom fields (lists, hirarchy, text).

### Out of scope

*   Central configuration of project dashboards

| Attribute | Value |
| --- | --- |
| Mockups |  |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap | 2027 Q4 |
| Date |  |
| Votes |  |
| List | RM Jira exit |
| Target versions |  |
| Sprint |  |
| Backlog bucket |  |
| Relevance | Medium — Useful Mid-Term |

## Subitems

_No work packages_

## Bugs and other work packages

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Enterprise plan |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable | Rosanna Sibora |
| Product manager | Sonita Soth |
| Feature Lead |  |
| Designer | Parimal Satyal |
| Developers | OP Dev Comms Team |
| Requested by |  |
| Interest by | Home (224196000003952096) |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work | 60d 0h |

## Description

Projects often share various settings. To keep them the same, similar projects shall be managed and centrally. This reduces errors and management effort.

**Example**

*   Flavour &quot;Agile&quot;: A agile project comes with the work package types EPIC, BUG, USER STORY etc. They usually need similar set of custom fields.
    
*   Flavour &quot;Risk management&quot;: Some projects need to do risk management. This requires another set of work package types, e.g RISK and another set of custom fields
    
*   A project can need both flavours at the same time. Both sets of settings need to be united.
    

<br>
