Skip to main content
Version: Release 22.2

Notifications

This topic describes how Digital.ai Release sends email notifications for certain events in a release. The default events include task level events and release level events.

Task level events​

  • Active task assigned: An active task has been assigned to somebody else. The new assignee receives an email telling them they are responsible for completion of this task. The task team members also receive an email notification.

  • Active task unassigned: The task owner and the task team receive an email telling them that the task must be assign to someone.

  • Comment added: When a user adds a comment to a task, an email is sent to the task owner and the task team members of the team assigned to the task. The author of the comment will not be notified.

  • Manual task started: Digital.ai Release started a task which is now in progress. Digital.ai Release sends a notification to the task owner.

    • If the task does not have an assignee but it has been assigned to a team, the task team members receive an email.
    • If there is no owner or team assigned, the release admin team receives an email that a task is in progress but no one is responsible for it. In the case of automated tasks, messages are sent to individual owners or team owners so they can track automated procedures they are responsible for. However, a warning message for unassigned tasks is not sent to release owners.

  • Manual task started without assignee: The release admin team receives and email that a manual task has started and there is no assigned task owner.

  • Task due soon: The release admin and the task owner receive and email when a task is approaching the set due date. The notification event triggers when only 25% of the initial task duration time remains.

    By default, the system checks for due soon tasks every 307 seconds. To change this interval, enter the following in the xl-release.conf with the required value.

 xl {
  	durations {
				notifyDueSoonTasksInterval = 307 seconds
		}
 }
note

It is recommended to keep the default settings. If you want to change the default settings, make sure that the time interval for notifyDueSoonTasksInterval is not the same as notifyOverduePlanItemsInterval to avoid excess load on the system.

  • Task failed: When a task fails, the task owner and the task team are notified so they can take action. A manual task fails when its owner indicates that he or she cannot proceed and clicks Fail. Automated tasks may fail when they cannot be executed correctly. If this results in a release failure, the release admin will receive an email.

  • Task flagged: The task owner and release admin receive an email when a user adds a flag status message to a task. If the task does not have an assigned owner, the task team receives the email notification. The author of the flag status message will not be notified.

  • Task overdue: The task owner and release admin receive an email that the task scheduled end date has passed and the task is overdue. If the task does not have an assigned owner, the task team receives the email notification.

    By default, the system checks for overdue tasks every 300 seconds. To change this interval, enter the following in the xl-release.conf with the required value.

xl {
 	durations {
			notifyOverduePlanItemsInterval = 300 seconds
		}
 }
note

It is recommended to keep the default settings. If you want to change the default settings, make sure that the time interval for notifyDueSoonTasksInterval is not the same as notifyOverduePlanItemsInterval to avoid excess load on the system.

  • Task waiting for input: The task owner and the task team receive an email that the task is waiting for input.

Release level events​

  • Release started: The release admin team is notified when a release has started.

  • Release completed: The release admin team is notified when a release is completed.

  • Release failed: The release admin team is notified when a release has failed.

  • Release failing: The release admin team is notified when a release is failing.

  • Release aborted: The release admin team is notified when a release was aborted.

  • Release flagged: The release admin team is notified when a user adds a flag status message to a task or the release to indicate that attention is needed or that the release is at risk. The author of the flag status message will not be notified.

note

When any action is performed on multiple releases at the same time, only one notification email is sent to each recipient containing the action performed and the list of releases.

Disable the Toggle feature for Overdue and Due-Soon Notifications​

To disable the toggle feature for overdue and due-soon notification jobs, enter the following in the xl-release.conf.

xl {
  features {
    notifications {
      due-soon {
        enabled = false
      }
      overdue {
        enabled = false
      }
    }
  }
}

Enable email notifications to inactive users​

Starting Digital.ai Release 10.1, by default, email notifications to inactive users are disabled. To enable email notification for inactive users, enter the following in xl-release.conf

xl {
  features {
        notifications {
            notify-inactive-users {
                enabled = true
      }
    }
  }
}

For more information about how to change the default notification settings, refer to Configure notification settings.

See Configure SMTP servers in Digital.ai Release for information about configuring the email server and sender for these messages.