Hi Jen, your response came through via email, so not sure if you meant to add here or message directly. Either way, to answer your two questions:
Have you run into any issues with deleting the Request? Loss of info, history, etc that you would've needed had you kept the original request? We're afraid of doing that and losing vital info. When you convert the project and opt to have it deleted, it does bring over all the information - documents, updates, etc. We just want to know which projects came in via the request queue vs. which were created as projects (usually internal, but not for legacy items), which is why I want the history. You do have to have a project version of any custom forms, though, to bring that data over. And the form needs to be tied to the project before you delete the request. It can be tied during the conversion process.
With the permissions change you suggested, how does that affect them in regards to putting in requests (if at all)? Our offenders are everybody at every access level (except administrators). Permissions can be set at a request-level so that it only affects that one request. As long as your queue settings note who can add requests, any other permission settings are per item (project, task, request). So, long story short - no effect to anything but the request(s) you want them to not comment on.
Overall, I would look at it like this:
If you want to keep the request record, don't tie the resolution and just manually close it.
If you don't care about the record (because the project pulls in updates, docs, etc.), opt to have it auto-delete.
Hope this helps!! Jazmin Allen-Collins Analog Devices, Inc.
