Content
View differences
Updated by Niels Lindenthal over 1 year ago
# User problem 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
# Business Case
## Reach
_About how many users, customers or potential customers currently have this problem? (Low / Worst Case)_
> Add this value to the custom field and delete this section.
## Impact
_Among relevant customers or prospects, how much value do they get from a comprehensive solution to this problem? (Conservative case)_
> Add this value to the custom field and delete this section.
## Confidence
_What are the top risk factors that could inhibit our ability to deliver this solution? Please consider how we can mitigate these risks._
> Add this value to the custom field and delete this section.
## Urgency and Priority
_What is the relative priority of this opportunity in your backlog? What tradeoffs must you make? Is there a hard deadline or could this wait?_
> Add this value to the custom field and delete this section.
## Solution
* For a specific work package type, the project admin can should be able to define composition compositions rules for the subject based on attributes and free text.
```text
{{projectValue:name}} - {{workPackage:Type}} - {{workPackageValue:ProzesskennungShort}} - {{workPackageValue:Version}}
```
* The composition should support hierarchical custom fields including selecting values or short forms from parent nodes.
* The admin should be able to mark the work package title is as **read only** to avoid manual violations of this rule. changes.
* The subject needs to be set on work package creation and any further updates of the attributes. update.
## Out of scope Scope for the MVC
_What should NOT be in the minimal viable change, and can be considered for future iterations? Why? Please order them by importance._
* Automatic file naming ...
## Acceptance criteria Differentiation
_What do you believe will differentiate us from the current experience or competitive experiences?_
* tbd ...
## Next iteration
_What is the next solution that would allow us to release meaningful customer value quickly?_
* ...
* <br>
# Launch and Growth
## Measures
* Adoption rate and retention could be good indicators.
## 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"><p class="op-uc-p">Headline</p></th><td class="op-uc-table--cell"><p class="op-uc-p">Ensure quality 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">Standardised title naming of specific work packages types.</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>
## Go to market
User discovery in work package type UI.
## Designs
<img class="image_resized op-uc-image op-uc-image_inline" style="width:552px;" src="/api/v3/attachments/95534/content"><img class="op-uc-image op-uc-image_inline">
## 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
_About how many users, customers or potential customers currently have this problem? (Low / Worst Case)_
> Add this value to the custom field and delete this section.
## Impact
_Among relevant customers or prospects, how much value do they get from a comprehensive solution to this problem? (Conservative case)_
> Add this value to the custom field and delete this section.
## Confidence
_What are the top risk factors that could inhibit our ability to deliver this solution? Please consider how we can mitigate these risks._
> Add this value to the custom field and delete this section.
## Urgency and Priority
_What is the relative priority of this opportunity in your backlog? What tradeoffs must you make? Is there a hard deadline or could this wait?_
> Add this value to the custom field and delete this section.
##
* For a specific work package type, the
```text
{{projectValue:name}} - {{workPackage:Type}} - {{workPackageValue:ProzesskennungShort}} - {{workPackageValue:Version}}
```
* The admin should be able to mark the
* The subject needs to be set on work package creation and any further updates of the attributes.
## Out of scope
## Acceptance criteria
## Next iteration
_What is the next solution that would allow us to release meaningful customer value quickly?_
* ...
* <br>
# Launch and Growth
## Measures
* Adoption rate and retention could be good indicators.
## 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"><p class="op-uc-p">Headline</p></th><td class="op-uc-table--cell"><p class="op-uc-p">Ensure quality 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">Standardised title naming of specific work packages types.</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>
## Go to market
User discovery in work package type UI.
## Designs
<img class="image_resized op-uc-image op-uc-image_inline" style="width:552px;" src="/api/v3/attachments/95534/content"><img class="op-uc-image op-uc-image_inline">