Make Request Queues Independent Of Projects

[#1]

We just had someone cancel the project that contains about 20 of our critical request queues.

It would be great to be able to create a queue on its own and then associate it with projects (like custom forms).

[#2]

Agreed. We have actually implemented something similar to what you're looking for but something like a backlog at the Project, Program, and Portfolio level would really helpful. Ideally a Portfolio backlog that would be filtered down for Programs and Projects. Especially for requests, this would be nice.

[#3]

Make it a point to remove "delete" from the project options. We do this for a variety of projects in order that they do not delete critical work.

[#4]

We created a template (with no tasks on it- so its just a shell of a template) that has all the needed RQs attached to it. Our PMs are instructed to attach this template to every project they open, and then they can create issues/requests for whatever they need (eg, Studio Spec Sheet, Art BUying, etc) and its tied to their project.