**As** a Begin of the insertionproject memberEnd of the insertion Begin of the deletion userEnd of the deletion
**I want to** see at least one high-level reason Begin of the insertionfor aEnd of the insertion Begin of the deletion ofEnd of the deletion why Begin of the insertionI am receiving aEnd of the insertion notification Begin of the deletion has been sentEnd of the deletion
**so that** I can evaluate Begin of the insertionitsEnd of the insertion Begin of the deletion theEnd of the deletion importance Begin of the insertionin relation to other notifications.End of the insertion Begin of the deletion of a notification.End of the deletion

Begin of the insertion<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/35007/content">End of the insertion Begin of the deletion <figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/22143/content"></div></figure>End of the deletion

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

* The Begin of the insertioncurrent format &quot;x hours ago by {user}&quot;End of the insertion Begin of the deletion authorEnd of the deletion is Begin of the insertionreplaced byEnd of the insertion Begin of the deletion shown asEnd of the deletion a Begin of the insertionmore complete form where at least one activity is specified.End of the insertion Begin of the deletion link with the name (instead of the avatar).End of the deletion
* The reason of the notification is shown in an abbreviated form Begin of the insertionthatEnd of the insertion Begin of the deletion
* The full list of what to render on every changedEnd of the deletion is Begin of the insertionstructure like this:End of the insertion Begin of the deletion below in the &quot;Update Strings&quot; sectionsEnd of the deletion
* Begin of the deletion Preliminary ideas:
* The preview is structured like:
* End of the deletion **Status** changed Begin of the deletion from NewEnd of the deletion to **Closed** Begin of the insertion(and 2 others),End of the insertion 1 hour ago by [Niels Begin of the insertionLindenthal](https://community.openproject.org/www.openproject.org).
End of the insertion Begin of the deletion Lindenthal](https://community.openproject.org/www.openproject.org) and 2 other notifications.
End of the deletion * Begin of the deletion For long texts and comments the diff is not shown.
* End of the deletion **Comment** added Begin of the insertion(andEnd of the insertion 1 Begin of the insertionother), 1End of the insertion hour ago by [Niels Begin of the insertionLindenthal.](https://community.openproject.org/www.openproject.org)
End of the insertion Begin of the deletion Lindenthal](https://community.openproject.org/www.openproject.org) and 2 other notifications.
End of the deletion * **Description** changed 1 hour ago by [Niels Begin of the insertionLindenthal](https://community.openproject.org/www.openproject.org).
End of the insertion Begin of the deletion Lindenthal](https://community.openproject.org/www.openproject.org) and 2 other notifications.
End of the deletion * **Subject** changed Begin of the insertion(and 4 others),End of the insertion 1 hour ago by [Niels Begin of the insertionLindenthal.](https://community.openproject.org/www.openproject.org)End of the insertion Begin of the deletion Lindenthal](https://community.openproject.org/www.openproject.org) and 2 other notifications.End of the deletion
* Begin of the insertionIn case ofEnd of the insertion Begin of the deletion The sorting is done, withinEnd of the deletion an aggregated journal entry, Begin of the deletion byEnd of the deletion the Begin of the insertionreason to be displayed follows this order of priority (in descending order):End of the insertion Begin of the deletion following priority:End of the deletion
* **User is @mentioned in a comment**
* **Assigned to Begin of the insertionuser**End of the insertion Begin of the deletion me**End of the deletion
* **Accountable set to Begin of the insertionuser**End of the insertion Begin of the deletion me**End of the deletion
* **Removed as assignee**
* **Removed as accountable**
* **Status changed**
* Begin of the insertion**DateEnd of the insertion Begin of the deletion **PriorityEnd of the deletion changed**
* Begin of the insertion**PriorityEnd of the insertion Begin of the deletion **VersionEnd of the deletion changed**
* Begin of the insertionVersion changed\*End of the insertion Begin of the deletion **Date changed**End of the deletion
* Begin of the insertionSubject changed\*End of the insertion Begin of the deletion **Subject changed**End of the deletion
* Begin of the insertionDescription changed\*End of the insertion Begin of the deletion **Description changed**End of the deletion
* **New comment(s)**
* **Assignee/Accountable changed (but not me)**
* Begin of the insertionFiles added\*End of the insertion Begin of the deletion **Files added**End of the deletion
* Begin of the insertionCustomEnd of the insertion Begin of the deletion **CustomEnd of the deletion fields Begin of the insertionchanged\*End of the insertion Begin of the deletion changed**End of the deletion
* Begin of the insertionParent changed\*End of the insertion Begin of the deletion **Parent changed**End of the deletion
* Begin of the insertion**\[open\]** Activities not in bold and marked an asterisk (\*) above currently do not generate a notification. Should these be added?
* End of the insertion The list of reasons to display is a closed set of events that the user has chosen to be notified about in their user settings. Begin of the insertionIt might not include allEnd of the insertion Begin of the deletion For any work package item in Notification Center, the listEnd of the deletion of Begin of the deletion reasons must ignoreEnd of the deletion the reasons Begin of the insertionlisted above:End of the insertion Begin of the deletion from the above priority list that do not interest the user.End of the deletion
* This means a lower-priority reason might actually be displayed instead of a higher priority one, if the user did not choose to be notified of that higher priority event. _Eg. if the user is has enabled notifications for &quot;all date changes&quot; and the work package has since also had a status Begin of the insertionchange (butEnd of the insertion Begin of the deletion change,End of the deletion the Begin of the insertionuser is not subscribed to these), theEnd of the insertion reason for notification remains the change of Begin of the insertiondate._End of the insertion Begin of the deletion date. This is because the list of reasons is limited (for that work package, depending on settings) to the list of subscribed reasons for being notified._End of the deletion
* If the work package is watched, all events are reasons for notification, so the entire list should be considered.
* These settings must take project-level settings into Begin of the insertionaccount;End of the insertion Begin of the deletion accountl;End of the deletion _eg. a work package in project A might have a different set of reasons for notification as project B._
* If the notification row aggregates multiple notifications, the change highest up in above&#39;s priority list is chosen. Begin of the deletion
* If two notification changes are tie for the same priority, the youngest one is used.
* The notification within the aggregated row from which the change is highlighted determine the user name and timestamp of the notification.
_E.g. in a notification row that aggregates a version being changed one hour ago by user A and a comment with a mention two hours ago by user B, the change will display a comment with a mention was done two hours ago by user B._End of the deletion
* The Begin of the deletion importance of journal changes is also applied to the aggreggated list of changes in the activity tab. 
_Eg. &quot;Assigned to&quot; is always rendered before &quot;Parent changed&quot;_
* TheEnd of the deletion details are displayed in the same way within each row of a reminder Begin of the insertionmail.End of the insertion Begin of the deletion mail End of the deletion

Begin of the insertion### **DetailEnd of the insertion Begin of the deletion **UpdateEnd of the deletion Strings**

_Notes_

* Brevity is prioritised so additional information is only provided where judged critical
* {time} is expressed relatively, as in &quot;3 hours ago&quot;
* {user} is expressed as a link
* The **parts in bold** are meant to really be in bold
* Begin of the insertionThe additional &quot;(and {n} others)&quot; or &quot;and 1 other&quot;) isEnd of the insertion Begin of the deletion I&#39;veEnd of the deletion not included Begin of the deletion the &quot;and {n} other notifications&quot;End of the deletion in these examples, but they would be present where Begin of the insertionrelevant.End of the insertion Begin of the deletion relevantEnd of the deletion

Begin of the insertion#### StringsEnd of the insertion Begin of the deletion _StringsEnd of the deletion (in order of Begin of the insertionpriority)End of the insertion Begin of the deletion priority)_End of the deletion

* _Comment with @mention_
**Mentioned** {time} by {user}
* _Assigned to me_
**Assigned to you** {time} by {user}
* _Accountable set to me_
**Accountable set to you** {time} by {user}
* _Assignee changed (from me to someone else)_
**Removed as assignee** {time} by {user}
* _Accountable changed (from me to someone else)_
**Removed as accountable** {time} by {user}
* _Status changed_
**Status Begin of the insertionchanged** to {new status}End of the insertion Begin of the deletion changed from {old status}**End of the deletion {time} by {user}
* _Priority changed_
**Priority Begin of the insertionchanged**End of the insertion Begin of the deletion changedEnd of the deletion to {new Begin of the insertionpriority}End of the insertion Begin of the deletion priority}**End of the deletion {time} by {user}
* _Version changed_
**Version Begin of the insertionchanged**End of the insertion Begin of the deletion changed from {old version}End of the deletion to {new Begin of the insertionversion}End of the insertion Begin of the deletion version}**End of the deletion {time} by {user}
* _Date changed_
**Date Begin of the insertionchanged**End of the insertion Begin of the deletion changedEnd of the deletion to {new Begin of the insertiondate}End of the insertion Begin of the deletion date}**End of the deletion {time} by {user}
* _Subject changed_
**Subject changed** {time} by {user}
* _Description changed_
**Description changed** {time} by {user}
* _New comment_
**New comment** {time} by {user}
* _Assigned changed (but unrelated to me)_
**Assignee Begin of the insertionchanged**End of the insertion Begin of the deletion setEnd of the deletion to {new Begin of the insertionuser}End of the insertion Begin of the deletion user}**End of the deletion {time} by {user}
* _Accountable changed (but unrelated to me)_
**Accountable Begin of the insertionchanged**End of the insertion Begin of the deletion setEnd of the deletion to {new Begin of the insertionuser}End of the insertion Begin of the deletion user}**End of the deletion {time} by {user}
* _Files added_
**New files added** {time} by {user}
* _Custom fields changed_
**{Custom field} updated** {time} by {user}
* _Parent changed_
**Parent changed** {time} by {user}

Begin of the insertion### Open questions (to be discussed)

* **\[open\]** Does the proposed priority order make sense (for aggregated journal entries)?
* **\[open\]** Does this syntax and phrasing work in other languages (need to test at least with DE, ES and FR)?
* The &quot;and 2 others&quot; bit is today appended at the end (eg. &quot;_14 hours ago by Marc Alcobé and 2 others&quot;_). However, this is confusing because it is unclear if &quot;2 others&quot; refers to two other users, or two other changes.
* To avoid the confusion, I propose &quot;Status changed to X (and 2 others), 14 hours ago by Marc Alcobé&quot; -- this way, we know that the 2 others refers to two other activities.
* **\[open\]** Is the list of reasons for notification exhaustive? What is missing?
* Missing because it generates a notification today for isn&#39;t on the list, or
* Mising because it doesn&#39;t curently geneate a notification but it _is_ on the list, or
* Missing because it is neither on this list nor does it currently generate a notification
* **\[open\]** We should surely update the notification card in the emails as well. Should we work on that in a separate ticket?

###End of the insertion **Out of scope**

* Begin of the insertionDate alerts (start or finish date approaching) remain a work in progress atEnd of the insertion Begin of the deletion ChangeEnd of the deletion the Begin of the insertionmoment. We can add it to the list once they are finalised.
* To stay coherent with the syntax described above though, they would take this form:
* **Start date** is in {n} days
* **Finish date** is in {n} days
* ~~Change theEnd of the insertion details in the daily email Begin of the insertion(~~_~~described in~~ ~~#38948)~~_End of the insertion Begin of the deletion (_described in <mention class="mention" data-id="38948" data-type="work_package" data-text="#38948">#38948</mention> )_End of the deletion