Content
View differences
Updated by Oliver Günther over 3 years ago
* If the card only displays a date alert
* Construct the relative time between the current time and the date referenced in the notification and display it as the third line.
* Hide the 'by user x' reference since no user will have triggered the notification
* If the card displays not only a date alert
* Use the 'by user x' message same as before.
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/37180/content"></div></figure> src="https://community.openproject.org/api/v3/attachments/37181/content"></div></figure>
* The _reason_ provided for a date alert notification (comparable to "mentioned" or "watched") will be "Date alert".
* When the user is inside the sidebar element "Date alert" the 3rd line of information always display the related info with the date alert in the style specified in the visuals. As the {time} is relative, this will change accordingly with the current date:
* "Start date is {time}" ("Start date was {time}" in case of past)
* "Finish date is {time}"
* Once the finish date is in the past, the work package is considered overdue: "Overdue since {time}"
* {time} is the relative difference between the current date and the set date in question
* In case the user is in any of the other sidebar elements (eg. Inbox) there are two possibilities:
* There is only one notification for the work package and it is a date alert: in this case the 3rd line will follow the same logic specified above.
* There is one date alert but also other notifications concerning that work package: the date alert isn't immediately visible, we will display the normal information "X days ago by Name Surname".
* In case start and finish date are on the same day and the configuration is also configured equally for both start and finish date, only display the finish date information as that one is more important.
* In the specific case of MILESTONES as they only have a single date, the finish date of the configuration will govern whether to create a notification.
* Display text that is specific to milestones: "Milestone date is {time}".
* Overdue should the same for milestone-typed WPs as for any other type.
* The information needs to reflect changes done to the work package after the notification is created.
* E.g. User is notified about the work package starting in 2 days. Another user moves the work package a week into the future. Then the notification card needs to say that it is starting in 9 days.
* Construct the relative time between the current time and the date referenced in the notification and display it as the third line.
* Hide the 'by user x' reference since no user will have triggered the notification
* If the card displays not only a date alert
* Use the 'by user x' message same as before.
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/37180/content"></div></figure>
* The _reason_ provided for a date alert notification (comparable to "mentioned" or "watched") will be "Date alert".
* When the user is inside the sidebar element "Date alert" the 3rd line of information always display the related info with the date alert in the style specified in the visuals. As the {time} is relative, this will change accordingly with the current date:
* "Start date is {time}" ("Start date was {time}" in case of past)
* "Finish date is {time}"
* Once the finish date is in the past, the work package is considered overdue: "Overdue since {time}"
* {time} is the relative difference between the current date and the set date in question
* In case the user is in any of the other sidebar elements (eg. Inbox) there are two possibilities:
* There is only one notification for the work package and it is a date alert: in this case the 3rd line will follow the same logic specified above.
* There is one date alert but also other notifications concerning that work package: the date alert isn't immediately visible, we will display the normal information "X days ago by Name Surname".
* In case start and finish date are on the same day and the configuration is also configured equally for both start and finish date, only display the finish date information as that one is more important.
* In the specific case of MILESTONES as they only have a single date, the finish date of the configuration will govern whether to create a notification.
* Display text that is specific to milestones: "Milestone date is {time}".
* Overdue should the same for milestone-typed WPs as for any other type.
* The information needs to reflect changes done to the work package after the notification is created.
* E.g. User is notified about the work package starting in 2 days. Another user moves the work package a week into the future. Then the notification card needs to say that it is starting in 9 days.