Why can a project be deleted if the tasks/issues have hours and the admin setup prevents deletion of tasks and issues with hours? It seems like this is just a miss in following through on the logic, right?

In the setup area under Project Preferences > Tasks & Issues, an admin can choose to allow or prevent deletion of tasks and issues with logged hours. My company does NOT allow for task/issue deletion if they have logged hours. This prevents folks from deleting things without having the necessary conversations to get time moved where it needs to go.

However, you can still delete the entire project - which is deleting the tasks/issues along with it! This seems like an oversight. If a company doesn't want tasks/issues deleted if they have hours, why would they ever want the whole project deleted instead?

I think Workfront needs to address this in the administrative setup. Either this single checkbox prevents project deletion as well or there needs to be another checkbox to prevent project deletion. There's literally no way to control whether someone deletes a project with time or not.

The hours are not permanently deleted - they're actually bumped to the General Hours line on a users timesheet. But this forces everyone down a path of correcting this type of mistake by hand for all users impacted (for all weeks impacted).

This obviously has huge impacts to reports as well. Want to know where your team was utilized? You won't be able to tell when this happens until after the time-consuming effort of fixing someone's simple mistake.

This seems like a pretty simple thing to fix. Can we get that in the roadmap?