Content
View differences
Updated by Oliver Günther about 3 hours ago
**As** an administrator a \[enter role of OpenProject user\]
**I want to** reuse a form configuration of another type but change it \[enter objective\]
**so that** I don't have to copy around too much \[enter desired result\]
In <mention class="mention" data-id="76544" data-type="work_package" data-text="##FND-102" data-display-id="FND-102">##FND-102</mention>, we will build a linking between types, so that I can reuse an existing form configuration 1:1 that will stay in sync.
From customer requirements, we have gathered that there may be need to do more, such as as
* reuse-but-extend: Keep the source form configuration and add fields to it
* reuse-and-limit: Keep the source form but disable certain attributes (That makes <mention class="mention" data-id="76674" data-type="work_package" data-text="##FND-134" data-display-id="FND-134">##FND-134</mention> possible)
**Acceptance criteria**
* In the form configuration step of the edit wizard, a third mode is possible (name something like Limit/Extend)
* In this mode, we keep the link select from a source
* Fields can be toggled of
* TBD: Users can inject fields into the form configuration
* How will they stay stable when the source changes?
**Technical notes**
* <br>
**Permissions and visibility considerations**
* _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_ languages_
**Out of scope**
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
**I want to** reuse a form configuration of another type but change it
**so that** I don't have to copy around too much
In <mention class="mention" data-id="76544" data-type="work_package" data-text="##FND-102" data-display-id="FND-102">##FND-102</mention>, we will build a linking between types, so that I can reuse an existing form configuration 1:1 that will stay in sync.
From customer requirements, we have gathered that there may be need to do more, such as
* reuse-but-extend: Keep the source form configuration and add fields to it
* reuse-and-limit: Keep the source form but disable certain attributes (That makes <mention class="mention" data-id="76674" data-type="work_package" data-text="##FND-134" data-display-id="FND-134">##FND-134</mention> possible)
**Acceptance criteria**
* In the form configuration step of the edit wizard, a third mode is possible (name something like Limit/Extend)
* In this mode, we keep the link select from a source
* Fields can be toggled of
* TBD: Users can inject fields into the form configuration
* How will they stay stable when the source changes?
**Technical notes**
* <br>
**Permissions and visibility considerations**
* _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._