Reason #2!

As an admin, I'm all for this so long as users can only restore things THEY deleted. In our instance, only admins can create templates, so some users have taken to creating "template projects" that run counter to policy. If an admin deletes something, we don't want it brought back.

Currently, there is no single place users can go to see their time off based on their schedule AND the time off they have personally opted to take. Displaying the time off from the user's schedule would make it much easier for them to manage their pto.

Thank you for the input @Madalyn_Destafney,. The issue we are running into is that while the system setting changes the default option, users can (and do) still change the setting on any given project. Being able to hide that option from view entirely (via layout templates) would solve this problem ...

The ability for end users to select "Ignore/Consider User Time Off" for task durations in projects can lead to unintended consequences if project owners don't fully understand what that field does. For companies where due dates can not be moved because a team member takes PTO, it is important that w...

100% agree. We should be able to disable ALL copy capabilities. I have submitted a similar idea, concerning task copying.https://one.workfront.com/s/idea/0874X000000oOsjQAE/detail

My organization is trying to enforce SOP and push the adoption of the templates we've developed. We have not allowed users to copy projects or to make their own templates, but they can (and do) still copy tasks rendering these other controls moot.

It would be great if we could target report emails to users the report applies to rather than it going to an entire group/team/user list.Example - a project report showing projects that are overdue by 10 days or more, sent weekly but only to the owners of those projects and their managers.The recipi...

Currently when you create a team, you are set as the team owner. My company only allows admins to create teams (ensuring consistency and reducing bloat) so creating a team is always a multi-step process: navigate to teams are, open new team, set members and options, search for the team you just made...

We can now set the "Work on It" button to be a "start" button, but it only seems to apply to tasks involving a team. It would be even better if we could set this as a global standard. Otherwise it can be confusing that tasks behave one way if only users are assigned, but behaves differently if there...