To further explain. Workfront release 1 is scheduled for April 26-27. Our board meeting is this week and we never deploy anything during board week. Workfront happened to choose our board week to deploy release 1. Some staff are concerned this may be disruptive if we encounter deployment and bug...

We would to be able and decide when we want to implement a release with new features. Maybe we want to push out new features that wouldn't have a huge impact on our business, but others will change the way we do business, so we'd like to be able to push those out when we are ready.

Same is happening in our organization, we need the ability to rename the "Subject" field.

We would like to be able to change the name of field "Subject" to something that makes more sense for our users. Each custom form could use different terminology, not just changing the term for all of our request forms.

Numerous users have asked for this.

This just happened today. A user arbitrarily added a random task and assigned it to someone. I know it's a training issue, but it would be great if we could stop users from doing that in the first place.

The ability to export a custom form into a PDF is much needed.

I agree! I learned by making errors.

This corresponds to an overarching integration we would like between projects, tasks, and issues. We would like to be able to create reports that intermix all three instead of being limited to creating a project report and then a separate issue report. Dashboards don't work since the two separate ...

Archiving projects and requests in Workfront is on my roadmap for next year, so it would be great if there were a built in way to archive.