Content
View differences
Updated by Robin Wagner over 4 years ago
**As** a project member
**I want** to see the project name along with shown in front of the related work package (both when selecting and viewing a work package)
**so that** I can easily see which project a work package belongs to (esp. for work packages with the same name in different projects).
**Acceptance criteria**
* Display project name along with in front of work package (or possibly behind to avoid issues with very long project names (or abbreviate project name)) when selecting a work package in the relations section.
* Display project name for related work packages.
* Display project name when selecting / viewing child work package hierarchies from relations section. (not directly requested but useful in terms of consistency)
**Mockup (preliminary)**
* Selecting relations:
<figure class="image op-uc-figure" style="width:50%;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/20036/content"></div></figure>
* Viewing relations:
<figure class="image op-uc-figure" style="width:50%;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/20038/content"></div></figure>
###
**Open**
* Does it make sense to re-use the auto-completer provided in the global search bar (which contains e.g. project information)?
### **User Problem**
#### **User**
_What persona, persona segment, or customer type experiences the problem most acutely?_
* Project managers who use project templates a lot and create work packages by the same name.
* e.g. project which contains engine-parts which are copied over.
#### **Problem**
_What problem or job does the user have?_
* Not clear which project a work package belongs to - especially if work packages have the same name.
* e.g. not clear which model (project name) a part (work package) belongs to.
#### **Pain**
_What is the primary workaround that users perform that we could remove or replace? Why is it painful?_
* The project name can be manually added to the name of the work package. This is however quite bothersome to add and can disrupt users working just within a project. It would also require that each time a project is created from a template, the names are manually adjusted for all work packages which reduces the benefit of using the template.
**I want** to see the project name along with
**so that** I can easily see which project a work package belongs to (esp. for work packages with the same name in different projects).
**Acceptance criteria**
* Display project name along with
* Display project name for related work packages.
* Display project name when selecting / viewing child work package hierarchies from relations section. (not directly requested but useful in terms of consistency)
**Mockup (preliminary)**
* Selecting relations:
<figure class="image op-uc-figure" style="width:50%;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/20036/content"></div></figure>
* Viewing relations:
<figure class="image op-uc-figure" style="width:50%;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/20038/content"></div></figure>
###
**Open**
* Does it make sense to re-use the auto-completer provided in the global search bar (which contains e.g. project information)?
### **User Problem**
#### **User**
_What persona, persona segment, or customer type experiences the problem most acutely?_
* Project managers who use project templates a lot and create work packages by the same name.
* e.g. project which contains engine-parts which are copied over.
#### **Problem**
_What problem or job does the user have?_
* Not clear which project a work package belongs to - especially if work packages have the same name.
* e.g. not clear which model (project name) a part (work package) belongs to.
#### **Pain**
_What is the primary workaround that users perform that we could remove or replace? Why is it painful?_
* The project name can be manually added to the name of the work package. This is however quite bothersome to add and can disrupt users working just within a project. It would also require that each time a project is created from a template, the names are manually adjusted for all work packages which reduces the benefit of using the template.