Keeping or not keeping original issue when coverting to Project?

[careyi]

Are most people keeping the original issue or removing the issue when converting to a Project. What we've found is people are confused as to where to add comments - do they comment on the issue, the task, the project, the doucment? What do people see as the Pro's & Con's of not keeping the Original issue?

[MartyGa]

We keep the original. It provides a clean connection to the end user who originally created the request. Additionally, we report off of the request type for certain queues which would get lost without keeping the original.

[NRYNR]

Here's what we do: Communication on the original issue with the requestor until all custom form edits and details are collected. Give the requestor "View" in sharing so we can eliminate changes after we've converted to a project. This notifies the requestor that their issue is "In Progress" automatically Project Sponsor is set to the requestor (so they can see all projects they sponsor in a dashboard) and so they get view rights to the project. All changes going forward are communicated on the project. However, sometimes the requestor posts updates on the original Issue, which is okay. As the PM, we make sure those translate to custom form edits on the project and/or documents. Complete the project (with Completion Mode always set to Automatic). This automatically resolves the Issue and notifies the requestor that their request is complete. This seems to work very well in our environment.