Issues converted to Projects

honestly, I would take it to the sandbox and try to replicate the error by either copying the issue and trying to convert that to project, or recreating the issue from scratch and trying to convert that to project. If you can do it with something else but just not that issue, you can start to narrow down the... uh... issue. -skye

Just woke up and I think I just figured out why! The hours that were on the issue were on a timesheet that was already submitted and approved. I will test this out when I get back to work - but I think this could be another Senior Moment! :-) Michael Gerrol Dell-RSA Security - IT

I just created an issue, logged a couple of hours on it, and then converted it to a project without keeping the original issue. There were no service error messages and my logged time is showing up in my new project under actual hours. So I think it's possible. Although how our settings differ or whether you have an issue with your permissions profile, would be a different question. -skye

Hi Christina, I got excited when I saw your response! So I tried that - but it only creates a project if I select the checkbox: 'Keep the original issue and tie its resolution to this project'. If I unselect that checkbox, and If there are Hours already logged to the issue I still get the error: "Let's try that again. The following error occurred: Service Error Message." Appreciate your help.... Does anyone else have that problem? -Mike Michael Gerrol Dell-RSA Security - IT

Michael, You want to change your timesheet & hour preferences to "Move any logged time to the project where the task or issue resides (If this task or issue is later restored, the time remains on the project)" It's under the very last section of 'When deleting tasks of issues...'. It should solve your problem. Christina Jarosz Ascensus

Hi all, We'd like to have an Issue deleted when it is converted to a project. However, we already have hours logged to the Issue and we receive an error when we try that. We don't want to lose the hours already logged to the issue and would like those hours applied to the newly created project instead. So is it true that we can't convert the issue to a project if there are hours already logged? If that's a known 'no-no' shouldn't there be a nice message stating that instead of the error message below: Many thanks in advance, -Mike Michael Gerrol Dell-RSA Security - IT

"You take the blue pill -the story ends, you wake up in your bed and believe whatever you want to believe. You take the red pill -you stay in Wonderland, and I show you how deep the rabbit hole goes..." Happy to help, Jill. Regards, Doug Doug Den Hoed - AtAppStore Got Skills? Lend a hand! https://community.workfront.com/participate/unanswered-threads

Doug that was a life changing moment when I changed that option to not keep the Issue when it's converted to a Project. THANK YOU. Jill Ackerman

Hi Jill, As attached (from Setup > Project Preferences > Tasks and Issues), Workfront is designed to let you choose whether or not to keep the original Issue when it gets converted to a Project (or Task), and can even add the Primary Contact to the Project automatically. I've found this approach works well where the conversion is effectively an "escalation" as it simplifies Workflow to consider the Project to BE the Issue, but now graduated into a Project, and (of course) it's ok for the Issue submitter to have access to the Project. Conversely, where the latter is NOT desired, it's likely wiser to preserve the original Issue and use the Resolving Object features As Designed to relay arms length status back to them as work progresses. Which of those constitutes Bad Side Effects is likely up to the person drinking the medicine.