Basic email template for notifications #96
No reviewers
Labels
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
Documentation
Type
Enhancement
Type
Feature
Type
Report
Type
Security
Type
Suggestion
Type
Testing
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/extensions-website#96
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "notification-templates"
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?
Based on the proposal #93
Email subjects change to the following:
Notification emails can also be viewed in the admin
Email previews
section (with fake objects constructed and passed into email template contexts):Indicating why the email was sent is not in this change because we currently don't store why precisely (can only guess it's either because of
moderators
group or extension follow, the state of either can change after the notification was generated). This can be part of theNotification
records however, after that the reason can be included in the email.WIP: Basic email template for notificationsto Basic email template for notifications