I pin a dashboard to the Projects area that includes a bunch of reports that filter to the user viewing it, including most of what you list above plus:My projects 100% complete but not in closed status (Yes, we're working toward defaulting all projects to autocomplete.)My projects not updated in ove...
My creative thinking: Create a queue for each visibility profile. You can aggregate intake by either routing requests to a central project or building a report/dashboard to report on the issues across the queues.
Theoretically, sure. I, however, have project owners who push back if there is any amount of redundancy. Those redundancies also mess with our reporting, which sends leadership in a tailspin.
That's my question, too. It sounds messy having to maintain two projects. I'd rather use a task conversion process. Cross-project predecessors, however—I'm trying to find the secret to recalculating schedules more automatically. I definitely support the concept of one deliverable per project for all...
I presume there is custom form data you're trying to carry over? If your custom form is applicable to tasks, you could add that custom data to a parent task and move the group of tasks to the monster project. I think. I hope. You might test it in the sandbox first.
Short of flipping the project condition to manual as @Kurt_Jones suggests, I personally would avoid tasks like you describe. Have you considered having people log time at the project level? Or use a different time category to differentiate project time versus meeting or admin time?
I support @Kurt_Jones suggestion. I'm starting change management to shut down the ability to create projects from scratch. One thing that will help quiet the haters: A template with no tasks. I have a generic portfolio with a program called "Unfiled projects" set as the default, which will help with...