Begin of the insertion**As an** administrator configuring any work package type (sub-type or plain type)End of the insertion Begin of the deletion **As** a \[enter role of user\]End of the deletion
**I want to** Begin of the insertionlink a type's workflow to a source type or make it independentEnd of the insertion Begin of the deletion \[enter objective\]End of the deletion
**so that** Begin of the insertionI can reuse the same exact workflow across many types without copying, or own my own workflow.End of the insertion Begin of the deletion \[enter desired result\]End of the deletion

Begin of the insertion## Acceptance criteriaEnd of the insertion Begin of the deletion **Acceptance criteria**End of the deletion

* Begin of the insertionFor any type, I can set its workflow to **Linked** (choosing a source type) or **Independent**. A sub-type defaults to Linked to its parent. _(F1-C0)_

End of the insertion Begin of the deletion <br>


**Technical notes**

End of the deletion * Begin of the insertionA Linked workflow resolves to its source at runtime; when I change the source&#39;s workflow, every linked type reflects it immediately. _(F1-C1)_

* When I switch a workflow to Independent, the system copies the current source&#39;s workflow once as a starting point and then severs the link. _(F1-C2)_

* The workflow matrix of a Linked type is read-only; I edit the owning (Independent) type instead, and the admin shows which source it is linked to. _(F1-C3)_

* The system prevents me from creating a cyclic dependency between workflow sources. _(F0-C2)_

* Linking a workflow never changes the type&#39;s display name or color. _(F0-C3)_End of the insertion Begin of the deletion <br>End of the deletion


Begin of the insertion## PermissionsEnd of the insertion Begin of the deletion **PermissionsEnd of the deletion and visibility Begin of the insertionconsiderationsEnd of the insertion Begin of the deletion considerations**End of the deletion

* Begin of the insertion**ToEnd of the insertion Begin of the deletion _ToEnd of the deletion whom is this feature Begin of the insertionvisible?** Users who can manage workflows or sub-types (admins; later project admins via `:manage_subtypes` for project-owned sub-types).End of the insertion Begin of the deletion visible?_End of the deletion

* Begin of the insertion**WhenEnd of the insertion Begin of the deletion _WhenEnd of the deletion is it not Begin of the insertionvisible?** Feature flag turned off, users without management rights. Linked types are read-onlyEnd of the insertion Begin of the deletion visible?_


**Translation considerations**

* _Key terms and phrasesEnd of the deletion in the Begin of the insertionworkflow matrix.End of the insertion Begin of the deletion key languages_&nbsp;End of the deletion


Begin of the insertion## Translation considerations

| English | German | French (verify) | Spanish (verify) |
|---|---|---|---|
| Workflow | Workflow | Workflow | Flujo de trabajo |
| Linked to {{type}} | Verknüpft mit {{type}} | Lié à {{type}} | Vinculado a {{type}} |
| Source type | Quelltyp | Type source | Tipo de origen |
| Use independent workflow | Unabhängigen Workflow verwenden | Utiliser un workflow indépendant | Usar un flujo de trabajo independiente |
| Copy workflow from type (one time) | Workflow einmalig von Typ kopieren | Copier le workflow depuis un type (une fois) | Copiar el flujo de trabajo de un tipo (una vez) |

## OutEnd of the insertion Begin of the deletion **OutEnd of the deletion of Begin of the insertionscopeEnd of the insertion Begin of the deletion scope**End of the deletion

* Begin of the insertionAdding a &quot;Extend&quot; reuse mode (only Linked or Independent for now).

* Merging or partially overriding a linked workflow.

* Defining multiple workflows per (sub-)typeEnd of the insertion Begin of the deletion <br>


_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._End of the deletion