infrastructure
/
extensions-website
4
6
Fork 4
Code Issues 20 Pull Requests Projects Releases Wiki Activity

Implement notifications #72

New Issue
Closed
opened 2024-04-08 15:31:14 +02:00 by Oleg-Komarov · 3 comments
Oleg-Komarov commented 2024-04-08 15:31:14 +02:00
Owner
Copy Link
  • Email
    • For moderators:
      • When a new extension is sent to approval queue.
      • When a review is reported.
      • When an extension is reported.
    • For owner of an extension:
      • When any activity happens on approval queue of your extension.
      • When any review happens on your extension.
    • For everyone:
      • When any activity happens after you interacted with the approval queue of an extension.?
  • Feed (similar to Blender Studio), keep all read notifications.
  • Profile setting to filter email notifications.

Notifications won't be batched in emails, each notification will generate a separate email message - this can be useful when using email as a task queue, when following up on a particular event, e.g. forwarding an email to someone, etc.

It is possible to unsubscribe from notification emails in the user profile. Emails will be sent only for users who have confirmed their email address.

* [x] Email * [x] For moderators: * [x] When a new extension is sent to approval queue. * [x] When a review is reported. * [x] When an extension is reported. * [x] For owner of an extension: * [x] When any activity happens on approval queue of your extension. * [x] When any review happens on your extension. * [x] For everyone: * [x] When any activity happens after you interacted with the approval queue of an extension.? * [x] Feed (similar to [Blender Studio](https://studio.blender.org/notifications/)), keep all read notifications. * [x] Profile setting to filter email notifications. Notifications won't be batched in emails, each notification will generate a separate email message - this can be useful when using email as a task queue, when following up on a particular event, e.g. forwarding an email to someone, etc. It is possible to unsubscribe from notification emails in the user profile. Emails will be sent only for users who have confirmed their email address.
Oleg-Komarov self-assigned this 2024-04-08 15:32:38 +02:00
Oleg-Komarov commented 2024-04-18 18:07:39 +02:00
Author
Owner
Copy Link

Deployed notification emails only for internal @blender.org email addresses.

Deployed notification emails only for internal `@blender.org` email addresses.
Oleg-Komarov commented 2024-04-19 17:07:42 +02:00
Author
Owner
Copy Link

Deployed a new notifications page and the navbar icon.

Deployed a new notifications page and the navbar icon.
Oleg-Komarov commented 2024-04-22 10:45:18 +02:00
Author
Owner
Copy Link

Deployed without the restriction for internal emails.

Deployed without the restriction for internal emails.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
production
teams-support
tos-flatpage
update-metadata-from-manifest
fix-thumbnails-edit
more-logging-context
other-services
releases
team
20240508-232058
20240508-221524
20240508-205611
20240425-132150
20240425-131144
20240425-102931
20240422-134616
20240422-084341
20240419-153008
20240419-150441
20240419-142636
20240419-103659
20240419-101459
20240419-091152
20240419-090459
20240418-155811
20240415-103440
20240411-125734
20240411-084629
20240405-171720
20240404-143833
20240404-073026
20240404-065215
20240402-155921
Labels
Clear labels   
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Normal
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

  
Type
Breaking
Breaking change that won't be backward compatible

  
Type
Bug
Something is not working

  
Type
Documentation
Documentation changes

  
Type
Enhancement
Improve existing functionality

  
Type
Feature
New functionality

  
Type
Security
This is security issue

  
Type
Testing
Issue or pull request related to testing

No Label
Priority
Critical
Priority
High
Priority
Low
Priority
Normal
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Type
Breaking
Type
Bug
Type
Documentation
Type
Enhancement
Type
Feature
Type
Security
Type
Testing
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
Oleg-Komarov
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: infrastructure/extensions-website#72
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?