Additional suffix for sender name of e-mail notifications originating from 'bitbucket.org'

Current feature:

During current usage of BitBucket Cloud notifications sent from:

#!
- <pullrequests-reply@bitbucket.org>
- <issues-reply@bitbucket.org>

... addresses use 'full name' specified through Atlassian account, i.e.

#!
Name Surname <pullrequests-reply@bitbucket.org>

Problem:

Since users commonly configure their own e-mail accounts to full name:

#!
Name Surname <name.surname@mail.example>

..., this occassionally leads project's collaborators to mistakenly send e-mails as replies to pull requests and/or issues, effectively littering them with often unrelated information.

This also can lead expected recipient to miss mailed information since (from my experience) Bitbucket Cloud doesn't seem to notify about such cases.

Potential solution:

If I remember correctly, Atlassian software that I've had access to few years ago appended suffix "(Stash)" to Stash's notifications sender name, resulting in:

#!
Name Surname (Stash) <...>

..., so such mistakes were practically absent.

Since Bitbucket Server possibly still offers similar solution by default, could it be also applied to Bitbucket Cloud, i.e. as:

#!
Name Surname (Bitbucket Cloud) <...>

...to remedy described problem?