Abstract: Automatic conversion of an email thread (or another form of electronic communication, such as IM chat content) into a collaborative workspace can begin with the detection of the addition of a reply message to an existing email thread by an email conversion handler. The existing email thread can include a main message and one or more reply messages. Satisfaction of user-defined or administrator-defined conversion criteria can then be assessed for the existing email thread. When the conversion criteria are satisfied, the existing email thread can be automatically converted into an artifact of a collaborative workspace contained within a collaborative environment. The collaborative workspace can be specific to the existing email thread. The designated participants of the existing email thread can be members of both the email and collaboration systems, and can be provided access to the collaborative workspace.

Abstract: Automatic conversion of an email thread (or another form of electronic communication, such as IM chat content) into a collaborative workspace can begin with the detection of the addition of a reply message to an existing email thread by an email conversion handler. The existing email thread can include a main message and one or more reply messages. Satisfaction of user-defined or administrator-defined conversion criteria can then be assessed for the existing email thread. When the conversion criteria are satisfied, the existing email thread can be automatically converted into an artifact of a collaborative workspace contained within a collaborative environment. The collaborative workspace can be specific to the existing email thread. The designated participants of the existing email thread can be members of both the email and collaboration systems, and can be provided access to the collaborative workspace.

Abstract: A computer-implemented method of task scheduling can include receiving an input from a user, wherein the input specifies a task comprising a due date and determining whether the task includes supplemental scheduling information. When the task does not include supplemental scheduling information, a first calendar event corresponding to the task can be created and stored within memory within a calendar of the user scheduled on the date. When the task does specify supplemental scheduling information, at least a first calendar event corresponding to the task can be created and stored, within memory, within a calendar of the user scheduled according to the date and the supplemental scheduling information. Calendar events created for a task that conflict with other calendar events can be dynamically rescheduled.