Yes! Proof statuses and proof deadlines in general need to be a more seamless experience in Workfront. If they are initiated through Workfront, you should be able to accurately track them through Workfront. The whole proofing experience still seems very separate.

I love this idea. We've been having a team member manually transfer this information from a request, into the project after conversion. This is not efficient.

Great idea! It would also be great if you could set specific dates for the year. For instance, we're required to report at the end of each fiscal month, which doesn't line up with the calendar months.

Yes! We're currently asking the business case questions on the custom intake form, and then MANUALLY transferring those responses to the business case after the project has been opened. It's so time consuming.

Yes! My clients have been asking for this since we implemented. The fields would only be mandatory if you were submitting. If you were saving we want the ability to leave fields blank.

For an immediate solution, I created a custom form with fields for a year, campaign number and job number. This form lives on all projects. Then I created a report titled "Next Job Number" and every time we resource a job, we also manually give it a job number (and fill in the year and campaign numb...

Yes! We also live and die by our job number and they quickly climbed to 6 digits. We also have been manually putting them in the project name, because there is no other place that has that immediate visibility.

I will also submit a feature request for it. Hopefully some additional support will get it moving faster. It's shocking to me that it's not a standard feature.

It is. We're running into issues where they're trying to shorten files names--while keeping all pertinent information. Also the PMs are used to having the project numbers burned into their brains, and 6 numbers is stretching their mental capacity, since they're used to 4 digit numbers. :-)

We've been using the reference number for a project as an identifying job number since our implementation. This was working OK--but after only 6 months in, the number is already 6 digits long, so we're on the hunt for another solution. Does anyone have any recommendations on how you populate job n...