For a different approach, you could look at doing something like we have done using an integration service (Azuqua) and email service (Mandrill-Mailchimp) to email your purchase orders from Workfront: Create custom fields to contain the PO-related data, including recipient email address info. ...

Just wondering why you need to rename 500 tasks on a weekly basis within this project? Perhaps there is another way to achieve the business requirement without needing to rename these tasks? If you can elaborate, someone may have a good idea. Another (fairly clunky) suggestion without using kickstar...

Whilst Giselle is one of the users who like some aspects of commit dates, she has hit on the key issues. I.e.: Once set, they don't change - even if the task is re-scheduled. They are very visible and can confuse users into thinking they are looking at when the task is due, when it is not.Then - a...

Just saw that system-wide widescreen is coming in 18.1! Woohoo! "https://support.workfront.com/hc/en-us/articles/115003927233#system-wide-widescreen-display">https://support.workfront.com/hc/en-us/articles/115003927233#system-wide-widescreen-display David Cornwell

Just saw that system-wide widescreen is coming in 18.1! Woohoo! https://support.workfront.com/hc/en-us/articles/115003927233#system-wide-widescreen-display

I also suggest milestones to signify the major events. In terms of notification of the publication to the external agencies (assuming they don't login to your Workfront system): Without using the API you could create a daily milestone report which identifies publishing milestone tasks with an Ac...

Yes please! We haven't been able to get any useable capacity/demand reporting out of Workfront to-date.

Hi - I've started a post on the Community asking for people's priorities on which screens they want converted to widescreen next. http://community.workfront.com/discussions/community-home/digestviewer/viewthread/?GroupId=151&MessageKey=601e5779-e462-4d41-88ba-f240ee01040f&CommunityKey=aaafaff0-5e4e-...

I'd really love to understand the logic of removing it. Was it really very difficult to maintain? Was it a third party license they didn't want to renew? Does it push some users towards ProofHQ somehow?

And/or, perhaps colour-code them so that you know easily which are standard and which are custom fields.