Begin of the insertion**As an** end user (and as an API consumer)End of the insertion Begin of the deletion **As** a \[enter role of user\]End of the deletion
**I want to** Begin of the insertionsee a sub-type under its parent type's name and color while still being able to discover the actual variationEnd of the insertion Begin of the deletion \[enter objective\]End of the deletion
**so that** Begin of the insertiondaily work stays simple and consistent, but the precise sub-type remains available when I need it.End of the insertion Begin of the deletion \[enter desired result\]End of the deletion

Begin of the insertion## Acceptance criteriaEnd of the insertion Begin of the deletion **Acceptance criteria**End of the deletion

* Begin of the insertionEverywhere in the product, a work package whose type is a sub-type shows the parent (root) name and color: type dropdowns, the work package table type column, cards, breadcrumbs, exports (PDF, Excel, CSV), notification emails, and activity entries

End of the insertion Begin of the deletion <br>


**Technical notes**

End of the deletion * Begin of the insertionThrough the API, a work package&#39;s `_links.type` and `/api/v3/types/:id` resolve to the actual sub-type, which exposes a `parent` link; the type id and href are stable and never contextual

* We need to use a displayName similar to the semantic ID for work packages

* Filtering a view by a parent type includes work packages of any of its sub-typesEnd of the insertion Begin of the deletion <br>End of the deletion


Begin of the insertion## PermissionsEnd of the insertion Begin of the deletion **PermissionsEnd of the deletion and visibility Begin of the insertionconsiderationsEnd of the insertion Begin of the deletion considerations**End of the deletion

* Begin of the insertion**ToEnd of the insertion Begin of the deletion _ToEnd of the deletion whom is this feature Begin of the insertionvisible?** All users who see types.End of the insertion Begin of the deletion visible?_End of the deletion

* Begin of the insertion**WhenEnd of the insertion Begin of the deletion _WhenEnd of the deletion is it not Begin of the insertionvisible?** Feature flag off (namesEnd of the insertion Begin of the deletion visible?_


**Translation considerations**

* _Key termsEnd of the deletion and Begin of the insertioncolors render fromEnd of the insertion Begin of the deletion phrases inEnd of the deletion the Begin of the insertionflat types).End of the insertion Begin of the deletion key languages_&nbsp;End of the deletion


Begin of the insertion## Open questionsEnd of the insertion Begin of the deletion **Out of scope**End of the deletion

* Begin of the insertion_when hoveringEnd of the insertion Begin of the deletion <br>


_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed ofEnd of the deletion the Begin of the insertiontype, we could reveal the actual sub-type name (&quot;Bug: Hardware&quot;)_End of the insertion Begin of the deletion changes._End of the deletion