In Adobe Workfront, an issue represents unplanned work, a bug, or a problem that needs to be addressed. When an issue requires more substantial effort than a simple fix, it can be escalated. The system provides two direct conversion paths for an issue: it can be converted into a task, which is then added to an existing project, or it can be converted into a new, standalone project. This allows teams to properly scope, plan, and track the resolution work using standard project management tools.

B. Update: An update is a comment or a status change associated with a work item; it is not a work object that an issue can be converted into.

D. Request: A request is an initial intake item submitted to a request queue. An issue is typically identified during a project, not converted back into a request.

1. Adobe Experience League Documentation, "Convert an issue in Adobe Workfront."

Reference: The introductory paragraph explicitly states: "You can convert an issue to a task or a project when you realize that the work required to complete the issue is more involved than you originally thought." This document details the procedures for both conversion types.

Source: https://experienceleague.adobe.com/docs/workfront/using/work-in-an-agile-environment/agile-issues/convert-issues.html?lang=en (Accessed under the sections "Convert an issue to a project" and "Convert an issue to a task").