Connect Request with Project without keeping the Request In Progress

Yes! Please make this enhancement! Keeping both the request and the project "In Progress" results in people add documents or put comments into the request instead of the project and those items fall through the cracks or if I uncheck the "Keep original issue" box, I don't have ANY request data that is vital for metrics reporting. The status of the request should be able to be changed independently of the status of the linked project without compromising the linkage.

YES - if necessary, a new status could be created, something like Converted. It would equate to Closed. But at a glance it would be obvious that it was not "fixed". It could also be reported against. I still think when the Resolving Object is Closed, that the original Request or Task be updated to Closed. Then you know it was finally fixed.

YES! Just emailed support about this. My team has the EXACT SAME issue that Donette's team has. People constantly add documents to the converted requests even though I explain (over and over) that once the request has been converted to a project the request should be considered "dead." If we could even filter the request screen so that only unconverted requests could be "seen" that would help a lot.

YES - Please make this change. I have the same problem. When we convert a request to a project or issue, we don't want it open in the Request queue because it will get updated in error & causes duplicate work. When converted it would be great to have the Converted status that Kathy states. Possibly a status of "Converted to Task" or "Converted to Project".

Now, I have my requests delete when converted - so I lose all those stats.

This is also confusing when the request has been converted to a task, both the request and the task show in the Home area. Once converted, the request should not show in the Home area as an open request.

This is one of the biggest pain points we have trying to roll out company wide communications controls. We need our requests to stay in their final status and close so we can track our SLA's. Right now we have to manually pull the information together outside of Workfront. It is not a good experience for our requestors when we having to break the link between request and project so they have to search for both.

The request staying open has created issues/lots of questions on our end. If there can be a separate status for the issue and not tied to the status of the project would be ideal. In addition the notifications cannot be turned of because they are tied to the notifications for tasks which we need to keep active, so separating the issues would be great.