Content
View differences
Updated by Dominic Bräunlein over 1 year ago
# User problem
## User
* Project manager
* Project member
## Problem
* The user needs to manually enter a subject for a work package according to specific pattern while all information that is needed to compose the subject is already present in work package attributes or other associated fields (projects, author, ...).
## Example
* The user creates a work package of type VACATION REQUEST
* This is needed for internal documentation of employee vacations
* The user needs to enter a subject for the work package according to a specific pattern
* At the same time the attributes needed to compose the subject are required anyway to further process the request
## Pain
* Right now the user needs to apply the pattern for subjects manually.
* The user needs to be informed about these patterns through alternative communication channels.
* Nobody enforces the pattern
* Therefore the user:
* needs to learn the pattern
* stay updated about the pattern
* apply it correctly
* Outdated subjects after the project manager changes a pattern
## Solution
* For a specific work package type, the admin can define composition rules for the subject based on attributes and free text.
```text
{{projectValue:name}} - {{workPackageValue:Type}} - {{workPackageValue:ProzesskennungShort}} - {{workPackageValue:Version}}
```
* The work package title is **read only** to avoid manual violations of this rule.
* The subject needs to be set on work package creation and any further updates of the attributes.
* The work package subject is defined in the work package type setting /types/3/edit/settings
* Admins can use OpenProject macros to compose rules
* Marcros need to be created for parent work package values and custom field of type hierarchy https://www.openproject.org/docs/user-guide/wysiwyg/#available-attributes-for-work-packages
## Out of scope for the MVC
* Automatic file naming
## Acceptance criteria
* tbd
## User
* Project manager
* Project member
## Problem
* The user needs to manually enter a subject for a work package according to specific pattern while all information that is needed to compose the subject is already present in work package attributes or other associated fields (projects, author, ...).
## Example
* The user creates a work package of type VACATION REQUEST
* This is needed for internal documentation of employee vacations
* The user needs to enter a subject for the work package according to a specific pattern
* At the same time the attributes needed to compose the subject are required anyway to further process the request
## Pain
* Right now the user needs to apply the pattern for subjects manually.
* The user needs to be informed about these patterns through alternative communication channels.
* Nobody enforces the pattern
* Therefore the user:
* needs to learn the pattern
* stay updated about the pattern
* apply it correctly
* Outdated subjects after the project manager changes a pattern
## Solution
* For a specific work package type, the admin can define composition rules for the subject based on attributes and free text.
```text
{{projectValue:name}} - {{workPackageValue:Type}} - {{workPackageValue:ProzesskennungShort}} - {{workPackageValue:Version}}
```
* The work package title is **read only** to avoid manual violations of this rule.
* The subject needs to be set on work package creation and any further updates of the attributes.
* The work package subject is defined in the work package type setting /types/3/edit/settings
* Admins can use OpenProject macros to compose rules
* Marcros need to be created for parent work package values and custom field of type hierarchy https://www.openproject.org/docs/user-guide/wysiwyg/#available-attributes-for-work-packages
## Out of scope for the MVC
* Automatic file naming
## Acceptance criteria
* tbd