Content
View differences
Updated by Judith Roth about 1 month ago
**As** a user of an instance that uses project-based semantic work package identifiers
**I want to** see project-based work package identifiers in the notification center and emails
**Acceptance criteria**
* If the instance is set to project-based work package identifiers
* emails (e.g. notifications) use the project-based work package identifier instead of the database ID
**Technical notes**
* <br>
**Permissions and visibility considerations**
* <br> _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* Previously, some strings to be translated _Key terms and phrases in the translations included the "#" before the global numeric identifier. Since the new project-based work package identifiers don't use a "#" any more, this was removed from the translations and is added programmatically if necessary (therefore, if a global numeric identifier is used instead of a project-based identifier). **Those translations need to be adapted - the # sign needs to be removed from the translation.** key languages_
**Out of scope**
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
**I want to** see project-based work package identifiers in the notification center and emails
**Acceptance criteria**
* If the instance is set to project-based work package identifiers
* emails (e.g. notifications) use the project-based work package identifier instead of the database ID
**Technical notes**
* <br>
**Permissions and visibility considerations**
* <br>
* _When is it not visible?_
**Translation considerations**
* Previously, some strings to be translated
**Out of scope**
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._