We have a request process. When a customer submits a request we either convert it to a task or a project. Either way - we lose the customer name / detail on the conversion. We need a field to have this information come over with the conversion.
As a work around to solve this need, we had to implement a required Primary Contact text custom field within the custom form that is attached to our tasks and/or projects which needs to be manually entered by the user when converting the issue object to a task or project.
Agreed! this is definitely necessary, even if it is a checkbox on conversion like "keep request/issue data upon conversion". Need to be able to see this data and report on it.
It would be great to not have to create a Primary Contact custom field and have the requestor add in their info again as it should be tracked as part of their user credentials.
