10 Notifications #

Click on the "Manage Your Notifications" link to define which notifications you want to receive. You can see this link in the "Actions" menu on your "Profile" page and on the "Notifications" page.

Figure 10.1: "Manage Your Notifications" link. #

 

On this page, you can configure under which conditions you receive each type of notification (email, RSS, web). Mark the "web" checkboxes to configure what notifications you will receive in the web UI.

Figure 10.2: Mark Web Notifications. #

 

You can get web notifications from events happening to projects and packages where the group you belong to is an owner. Just mark the "web" checkbox in the groups your are interested in.

Figure 10.3: Mark Web Notifications for Groups. #

 

At the top right corner of every page, you will find a link to your notifications. It includes a counter of your unread notifications. Just click on it to access your notifications page.

Figure 10.4: Notifications Link. #

 

After clicking on the "Notifications" link, you will see a list of your most recent unread notifications.

Figure 10.5: Notifications Page. #

 

A notification can have different origins. Each notification item includes a couple of lines to help recognize them among the others. You always have the option to click on a notification, which will lead you to the specific section of OBS (request, comment, project, package, ...) with the full details on what caused the notification.

Once you read a notification and possibly take action, you can mark it as read. This will sort the notification in the "read" category and it's not shown anymore next to the one that might still need some attention. Also worth mentioning that we perform a periodical cleanup that deletes all the notifications older than 365 days.

There are different ways and places to mark your notifications as read. Marking a single notification can be done by simply clicking the button with the green checkmark shown on the notification itself.

Figure 10.6: Mark single notification as read. #

 

Another way is to mark it directly on the related element (for example the associated request) through the little toolbar that appears on top. You will be redirected back to your notifications page afterwards.

Figure 10.7: Mark notification as read through toolbar. #

 

If you received a lot of notifications and don't want to mark them one by one, there are two ways to speed up the process. You can use the checkboxes on the left to select individual notifications and click on the "Mark selected as 'Read'" button.

Figure 10.8: Checkboxes to mark multiple notifications. #

 

In case you exceed 300 notifications you have the possibility to use the button "Mark all as 'Read" that will appear on the right side to mark all notifications of the chosen filter as read.

Figure 10.9: Mark all as read. #

 

Should you ever mark a notification as read by accident, you can simply revert this by selecting the "read" filter on the right side and using the equivalent elements, used to mark them as read, in order to bring them back to your unread notifications.

Filters help you in focusing your attention on a subset of your notifications. They are on the left side of your screen.

Figure 10.10: Example of notification filters. #

 

Here's a description of all available filters:

Every user can check their unread notifications by querying:

osc api -X GET "/my/notifications"

It will return a list with your unread notifications:

<?xml version="1.0" encoding="UTF-8"?>
<notifications count="2">
    <total_pages>1</total_pages>
    <current_page>0</current_page>
    <notification id="3">
        <title>test 1</title>
        <who>Administrator</who>
        <state>new</state>
        <when/>
        <event_type>review_wanted</event_type>
    </notification>
    <notification id="25">
        <title>test 2</title>
        <who>User 2</who>
        <event_type>comment_for_package</event_type>
        <when/>
    </notification>
</notifications>

This one will toggle a notification read or unread.

osc api -X PUT "/my/notifications/3"

It will say if the operation went well or not.

<?xml version="1.0" encoding="UTF-8"?>
<status code="ok">
    <summary>Ok</summary>
</status>

For more informtion regarding the notifications API endpoints, check out our New API Documentation.