Updated in order.  Closing out old timesheets that are open or deleting timesheets without hours logged. AND making sure users don't get notified of those actions.Archiving teams, templates, boards that haven't been used in x amount of timeAuto deactivate users or downgrade access levels after x tim...

Adding of Template Tasks once a certain task has been completed or task approval made, allowing for different directions of the project based on previous actions.    This would be great to help with iterations within the waterfall project lifecycle, which is a gap in functionality for some clients. ...

All things related to the Administration of Workfront.   Auto deactivate users or downgrade access levels after x time of not logging in or performing actions necessary for the license typeClosing out old timesheets that are open or deleting timesheets without hours logged. AND making sure users don...

Purging data based on company retention policy. examples: deleting documents or projects after x years. 

When I had one it was modeled after a NPS Survey (Net Promoter Score) so we could gauge promoters and detractors.   We started with a 0-10 question: On a scale from 0-10, how likely are you to recommend Workfront to a friend or colleague? Then, please tell us why you gave a rating.   Then we narrowe...

Yes! I'm planning on coming! 

Agreed and we aren't changing anything just wanted to hear some pros and cons since I've never heard anyone say it before.

I'm gonna run some reports to see if the tasks still show as pending predecessors, etc to double check. Thank you.

That is good to know and something I will definitely test and look into. Thank you.

I was on a call recently where someone from Workfront mentioned it wasn't good practice to use Parent tasks as Predecessors.  We do this pretty regularly since often times the tasks nested under a parent all need to be completed in order for the next tasks to start. So, instead of listing every sing...