Project

General

Profile

Actions
Copy link

Tracker #7662

closed

Email Notifications

Added by Eric Helms about 10 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Errata Management
Target version:
Katello Recycle Bin
% Done:

0%

Difficulty:
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Related issues 10 (0 open — 10 closed)

Related to Foreman - Feature #153: Notifications when hosts report failuresClosedJosh Baird01/11/2010Actions
Blocked by Foreman - Feature #7663: As an API user, I should be able to manage my own email notification preferences.Closed09/26/2014Actions
Blocked by Foreman - Feature #7664: As a UI user, I should be able to manage my own email notification preferences.Duplicate09/26/2014Actions
Blocked by Katello - Feature #7666: As a user, I should be able to receive an email after every sync operation based upon my preferences.Closed09/26/2014Actions
Blocked by Katello - Feature #7667: As a user, I should be able to receive an email after every promote operation based upon my preferences.Closed09/26/2014Actions
Blocked by Katello - Feature #7668: As a user, I should be able to receive a daily email of my visible hosts and available errata grouped by organization based upon my preferences.Closed09/26/2014Actions
Blocked by Foreman - Feature #7672: As a user, I should be able to receive an email after a Puppet report error.Closed09/26/2014Actions
Blocked by Katello - Feature #7713: A user should only receive errata notifications for repositories and content views that the user has view access to.ClosedStephen Benjamin09/26/2014Actions
Blocked by Katello - Feature #7714: A user should only receive content host notifications for content hosts that the user has view access to.ClosedStephen Benjamin09/26/2014Actions
Blocked by Foreman - Feature #7586: As a UI user, I want to configure which e-mails notifications to receiveClosedStephen Benjamin09/23/2014Actions
Actions
Copy link
 #1

Updated by Eric Helms about 10 years ago

  • Blocked by Feature #7663: As an API user, I should be able to manage my own email notification preferences. added
Actions
Copy link
 #2

Updated by Eric Helms about 10 years ago

  • Blocked by Feature #7664: As a UI user, I should be able to manage my own email notification preferences. added
Actions
Copy link
 #3

Updated by Eric Helms about 10 years ago

  • Blocked by Feature #7665: As a CLI user, I should be able to manage my own email notification preferences. added
Actions
Copy link
 #4

Updated by Eric Helms about 10 years ago

  • Blocked by Feature #7666: As a user, I should be able to receive an email after every sync operation based upon my preferences. added
Actions
Copy link
 #5

Updated by Eric Helms about 10 years ago

  • Blocked by Feature #7667: As a user, I should be able to receive an email after every promote operation based upon my preferences. added
Actions
Copy link
 #6

Updated by Eric Helms about 10 years ago

  • Blocked by Feature #7668: As a user, I should be able to receive a daily email of my visible hosts and available errata grouped by organization based upon my preferences. added
Actions
Copy link
 #10

Updated by Eric Helms about 10 years ago

  • Subject changed from Errata Notifications to Email Notifications
Actions
Copy link
 #11

Updated by Eric Helms about 10 years ago

  • Related to Feature #7672: As a user, I should be able to receive an email after a Puppet report error. added
Actions
Copy link
 #12

Updated by Eric Helms about 10 years ago

  • Related to deleted (Feature #7672: As a user, I should be able to receive an email after a Puppet report error.)
Actions
Copy link
 #13

Updated by Eric Helms about 10 years ago

  • Blocked by Feature #7672: As a user, I should be able to receive an email after a Puppet report error. added
Actions
Copy link
 #14

Updated by Eric Helms about 10 years ago

  • Related to Feature #153: Notifications when hosts report failures added
Actions
Copy link
 #16

Updated by Eric Helms about 10 years ago

  • Blocked by Feature #7713: A user should only receive errata notifications for repositories and content views that the user has view access to. added
Actions
Copy link
 #17

Updated by Eric Helms about 10 years ago

  • Blocked by Feature #7714: A user should only receive content host notifications for content hosts that the user has view access to. added
Actions
Copy link
 #18

Updated by Stephen Benjamin about 10 years ago

  • Blocked by Feature #7586: As a UI user, I want to configure which e-mails notifications to receive added
Actions
Copy link
 #19

Updated by Walden Raines about 10 years ago

  • Category set to Errata Management
Actions
Copy link
 #20

Updated by Eric Helms almost 10 years ago

  • Translation missing: en.field_release changed from 14 to 23
Actions
Copy link
 #21

Updated by Eric Helms almost 10 years ago

  • Translation missing: en.field_release deleted (23)
Actions
Copy link
 #22

Updated by Eric Helms almost 9 years ago

  • Blocked by deleted (Feature #7665: As a CLI user, I should be able to manage my own email notification preferences.)
Actions
Copy link
 #23

Updated by Eric Helms almost 9 years ago

  • Status changed from New to Resolved
Actions
Copy link
 #24

Updated by Eric Helms over 8 years ago

  • Translation missing: en.field_release set to 166
Actions
Copy link

Also available in: Atom PDF