Content
View differences
Updated by Marc Alcobé over 3 years ago
**As** a user
**I want to** have a clear understanding where a work package is located
**so that** I'm sure I'm working on the correct instance, project, parent and work package
## **Acceptance criteria**
* The breadcrumb is updated to indicate the project that the work package is set on. Only the project that contains the work package is shown, even if this is a sub-project.
* After the project there is the option to set a parent for it (or the parent if it already has one). one).
* Once the set parent is filled it might happen that the parent work package belongs to a different parent than the child (see specific visuals bellow for set parents flow and cases).
* In case of accessing a work package from outside any project the blue box with "This work package belongs to project X. Open this work package in that project." will not appear anymore as you can see the project in the breadcrumb.
* There is a specified (configurable per view) number of levels shown. If there is more than this levels a second level with "..." will appear collapsing the levels in between. (see "Long breadcrumb visuals")
* The breadcrumb has some configurable elements from a code perspective:
* Configurations for the complete breadcrumb:
* How many levels are shown before showing the truncate level (in this case: 5 levels).
* Does the breadcrumb show the current level (in this case: no, as it would duplicate the work package subject).
* Configurations for each level of the breadcrumb:
* A non mandatory and non-clickable label (in this case appears for the "Parent:" work packages).
* A non mandatory and clickable icon that has the same link as the text (in this case appears in the first level to indicate that is a project).
* A mandatory and clickable link text (only exception is the current level that is not clickable).
* Once the parent is set and "outside of the breadcrumb" the actions to edit or remove the parent will be added.
* The logic for long breadcrumbs is taken from the one already implemented on file/location picker: If even with the "..." level the breadcrumb exceeds the total screen width, all the levels shown will start truncating at the same % adding at the end of each also the "...". (see "Long breadcrumb visuals").
## Visuals
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/38527/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/38528/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/38940/content"><img src="/api/v3/attachments/38529/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/38530/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/38531/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/38532/content">
## Long breadcrumb visuals
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/38938/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/38939/content">
**I want to** have a clear understanding where a work package is located
**so that** I'm sure I'm working on the correct instance, project, parent and work package
## **Acceptance criteria**
* The breadcrumb is updated to indicate the project that the work package is set on. Only the project that contains the work package is shown, even if this is a sub-project.
* After the project there is the option to set a parent for it (or the parent if it already has one).
* Once the set parent is filled it might happen that the parent work package belongs to a different parent than the child (see specific visuals bellow for set parents flow and cases).
* In case of accessing a work package from outside any project the blue box with "This work package belongs to project X. Open this work package in that project." will not appear anymore as you can see the project in the breadcrumb.
* There is a specified (configurable per view) number of levels shown. If there is more than this levels a second level with "..." will appear collapsing the levels in between. (see "Long breadcrumb visuals")
* The breadcrumb has some configurable elements from a code perspective:
* Configurations for the complete breadcrumb:
* How many levels are shown before showing the truncate level (in this case: 5 levels).
* Does the breadcrumb show the current level (in this case: no, as it would duplicate the work package subject).
* Configurations for each level of the breadcrumb:
* A non mandatory and non-clickable label (in this case appears for the "Parent:" work packages).
* A non mandatory and clickable icon that has the same link as the text (in this case appears in the first level to indicate that is a project).
* A mandatory and clickable link text (only exception is the current level that is not clickable).
* Once the parent is set and "outside of the breadcrumb" the actions to edit or remove the parent will be added.
* The logic for long breadcrumbs is taken from the one already implemented on file/location picker: If even with the "..." level the breadcrumb exceeds the total screen width, all the levels shown will start truncating at the same % adding at the end of each also the "...". (see "Long breadcrumb visuals").
## Visuals
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/38527/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/38528/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/38940/content"><img
## Long breadcrumb visuals
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/38938/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/38939/content">