Conversion Mapping from Incidents to Projects or Tasks

How to Manage Incidents › Convert Unplanned Incidents into Planned Project Work › Conversion Mapping from Incidents to Projects or Tasks

Conversion Mapping from Incidents to Projects or Tasks

When you convert an incident to a project or a project task, some data is carried forward with the incident to the new project. The following table shows how the data maps when converted:

Incident Data Field	Project Data Field	Project Task Field
Short Description	Project Name	Name
Tracking ID	Project ID	ID
Status	Status (Unapproved)	Status (Not Started)
Detailed Description	Description	N/A
Assigned Project Manager	Manager	N/A
Start date	Start Date	Start (date)
Expected End date	Finish Date	Finish (date)

The following exceptions apply:

Effort data is not carried forward to the project or project task during conversion. The time you spend and enter for the incident does not get carried forward when the incident is converted. The incident effort and the new project or task effort represent separate activities and are time-tracked separately.
Any custom attributes on the Incident object do not convert to identical custom attributes on the project or task.
If the contact or assigned resource is not a team member of the project, data does not carry forward.
When you convert an incident into a project or project task, you cannot link back to the incident from the project or project task. A link exists only from the incident to the converted project or project task.