The initial step of important collaborations start over an email, and most of these require an immediate follow-up by creating a task, or reporting an issue. During these instances, an
email alias helps users add the required work items to the project by sending an email.
Consider a Security Operations analyst receiving an incident alert towards the end of their shift. Before handover, they log pending alerts and unresolved incidents. They send an email to the task alias with the incident details and the required dates, include the
L3 analyst for review, and
CC the members of the next shift. The
task is created and assigned to the users in
CC, while the
L3 analyst gets a heads-up with the incident details for review. The next shift can then pick up the work where it was left off.