# User problem

## User

* Begin of the insertion**Admins:** Want to enforce specific naming conventions for certain work package types (e.g., invoices, vacation requests).End of the insertion Begin of the deletion Project managerEnd of the deletion

* Begin of the insertion**Project Members:** Need consistent titles to identify and process specific work packages.End of the insertion Begin of the deletion Project memberEnd of the deletion


## Problem

* Begin of the insertionCurrently, users can input any titleEnd of the insertion Begin of the deletion The user needs to manually enter a subjectEnd of the deletion for a work Begin of the insertionpackage, leadingEnd of the insertion Begin of the deletion package accordingEnd of the deletion to Begin of the insertioninconsistencies. For certain types ofEnd of the insertion Begin of the deletion specific pattern while all information that is needed to compose the subject is already present inEnd of the deletion work Begin of the insertionpackages e.g. invoicesEnd of the insertion Begin of the deletion package attributesEnd of the deletion or Begin of the insertionvacation requests, admins want predefined title patterns to maintain uniformity and avoid errors. These patterns must include relevant attributes (e.g., author name, project name, date) but are not enforced in the current system.End of the insertion Begin of the deletion other associated fields (projects, author, ...).End of the deletion


Begin of the insertion####End of the insertion Begin of the deletion ##End of the deletion 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

* Begin of the insertionPatterns are applied inconsistently, and updatesEnd of the insertion Begin of the deletion Right now the user needsEnd of the deletion to Begin of the deletion apply the pattern for subjects manually.

* The user needs to be informed about theseEnd of the deletion patterns Begin of the insertionare not reflected in existing titles.End of the insertion Begin of the deletion through alternative communication channels.End of the deletion

* Begin of the insertionUsers must rely on verbal or written instructionsEnd of the insertion Begin of the deletion Nobody enforces the pattern

* Therefore the user:

* needsEnd of the deletion to Begin of the deletion learn the pattern

* stay updated about the pattern

* End of the deletion apply Begin of the insertionpatterns, which may not always be accurate or up to date.

<br>End of the insertion Begin of the deletion it correctly

* Outdated subjects after the project manager changes a patternEnd of the deletion


## Solution

* Begin of the insertion**Subject Patterns for Work Package Types**

* AdminsEnd of the insertion Begin of the deletion For a specific work package type, the adminEnd of the deletion can define Begin of the insertiontitleEnd of the insertion composition rules for Begin of the insertionspecific work package types via a settings page.

* Example:&nbsp;
`{{projectValue:name}}End of the insertion Begin of the deletion the subject based on attributes and free text.


```text
{{projectValue:name}}End of the deletion - {{workPackageValue:Type}} - Begin of the insertion{{workPackageValue:CustomFieldName}}`.

End of the insertion Begin of the deletion {{workPackageValue:ProzesskennungShort}} - {{workPackageValue:Version}}
```

End of the deletion * Begin of the insertion**Enforced Titles**

End of the insertion Begin of the deletion The work package title is **read only** to avoid manual violations of this rule.

End of the deletion * Begin of the insertionTitles for these specific types are automatically generatedEnd of the insertion Begin of the deletion The subject needs to be set on work package creationEnd of the deletion and Begin of the insertionread-only.

* **Dynamic Updates**

* TitleEnd of the insertion Begin of the deletion any furtherEnd of the deletion updates Begin of the insertionautomatically when referenced attributes (e.g., project name, date) are changed. (to be discussed)

End of the insertion Begin of the deletion of the attributes.

End of the deletion * Begin of the insertion**Configuration Location**

* Patterns are set underEnd of the insertion Begin of the deletion The work package subject is defined inEnd of the deletion the work package type Begin of the insertionsettings (`/types/:id/edit/settings`).

End of the insertion Begin of the deletion setting /types/3/edit/settings

End of the deletion * Begin of the insertion**Marcros**

End of the insertion Begin of the deletion Admins can use OpenProject macros to compose rules

End of the deletion * Begin of the insertionAdditional macrosEnd of the insertion Begin of the deletion MarcrosEnd of the deletion 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 Begin of the insertion


End of the insertion Begin of the deletion


End of the deletion ## Out of scope for the MVC

* Automatic file naming


Begin of the insertion# Launch and Growth

End of the insertion ## Begin of the insertionMeasuresEnd of the insertion Begin of the deletion Acceptance criteriaEnd of the deletion

* Begin of the insertionIncrease in consistency for specific work package types.

* Reduction in user errors when creating work package titles.

* Feedback from admins on ease of setup and usage.


## Messaging

<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><tbody><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head" style="width:150px;"><p class="op-uc-p">Headline</p></th><td class="op-uc-table--cell"><p class="op-uc-p">Take control of work package titles</p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">First Paragraph</p></th><td class="op-uc-table--cell"><p class="op-uc-p">With OpenProject's new automated subject patterns, you can ensure consistent naming conventions for specific work package types like invoices, vacation requests, and more. Say goodbye to manual errors and hello to streamlined workflows!</p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Customer Quote</p></th><td class="op-uc-table--cell"><p class="op-uc-p"><br></p></td></tr></tbody></table></figure><br>

## Go to market

* Feature announcement in release notes and newsletters.

* Detailed user guide with examples of pattern usage.

<br>End of the insertion Begin of the deletion tbdEnd of the deletion